Post #3326043
2026-06-15 14:52 UTC
That is a feature. Allowing arbitrary programs to read any key press is how you get keyloggers.
Wayland has a protocol to request reading keys out of focus (which will ask the user for permission, as opposed to just read it like on xorg).
If the program was running in xwayland (which it probably was) of course it won’t use that protocol, and will just try to read it X11 style.
In some DEs (KDE) you can select if X11 apps are allowed to read keys.
“I switched to X11 and it immediately works”. I’ll give you another tip: if you run chmod 777 -R / the file manager stops pestering about permissions and it immediately works.
Replies (1)
-
@rihatsu@lemmy.zip 2026-06-15 16:54
Yes, you clearly understand the problem, thank you. If there’s a problem with filesystem permissions you can use tools like chmod, chown, and setfacl to fix them in a variety of ways. How do you fix a wayland session if your app doesn’t properly support GlobalShortcuts? Where’s the chmod 777 equivalent that lets the user say “I know this means this can spy on everything I do but I’d prefer this work today instead of waiting on a bug fix.” Without something like this, the entire desktop ecosystem needs to mature before you can call Wayland “polished.”