Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support wayland a little bit more clearly #223

Open
Connor-GH opened this issue Jan 3, 2024 · 2 comments
Open

Support wayland a little bit more clearly #223

Connor-GH opened this issue Jan 3, 2024 · 2 comments

Comments

@Connor-GH
Copy link

I recently purchased a Launch Lite. The AppImage refused to open, citing "Failed to initialize GTK" even though I knew I had all of the libraries installed. After recompiling Rust, gtk3, glib, cairo, installing gtk4 (even though it wasn't needed; done as a sanity check), I realized it was a wayland thing. Running the appimage with "xhost + local; ..." fixes the issue, but this was not clear at all. Using the privilege escalation in the application itself did not work for me OOTB, citing that "this incident will be reported" and such even though i'm in the wheel group and used the right password.

@bugsbugsbux
Copy link

I use sway on nixos and had to run the following to get it to work:

nix-shell -p xorg.xhost;
xhost +si:localuser:root;
sudo system76-keyboard-configurator

would be nice if the xhost stuff could be mentioned in the readme somewhere

@ids1024
Copy link
Member

ids1024 commented Dec 27, 2024

If a polkit agent is running, keyboard-configuration should show a dialog to grant permission. Then works fine natively on Wayland.

Perhaps this could be handled better, though I think anything would either require a polkit agent, or a custom root daemon/suid helper.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants