'Super' Key Stuck When Using Application Launcher 'Fuzzel' #11397
Unanswered
Jazztache
asked this question in
Bugs - Input
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello!
One application in particular seems to be causing me trouble. I have reason to suspect it is an issue with Hyprland and not something specific to this application.
I have already contacted the developer about this and they say it is likely some kind of Wayland/Hyprland issue.
The application is called Fuzzel, and there is some weird behavior related to keybinds and configs. I have a particular bind in my config:
bind = $mainMod, TAB, exec, killall fuzzel || fuzzel --log-level=info # Meta + Tab is used for fuzzel.
Note that my $mainMod key is the 'Super' or 'Meta' key.
The original issue report I made is here: https://codeberg.org/dnkl/fuzzel/issues/534
I decided to wait a few versions to see if some internal change would fix this, but even on Hyprland 0.50, the error is still there.
This is why I am bringing it up now, and here.
Launching fuzzel from the config using Super + Tab makes it so that the Super key is 'stuck' down. Clicking the left mouse button picks up windows, and I cannot press ESC to close the Fuzzel window like I usually can. Every keystroke acts like I am holding down the Super key whilst typing.
This usually lasts for an amount of time. I am not sure what triggers it to realise that the key is stuck down and fix it.
Strangely, fuzzel seems to occasionally work normally when launched in a terminal.
When launched raw using
bind
in Hyprland, the odd 'Meta key stuck' behaviour always happens.Additionally, pressing the bind again to kill the application seems to de-stick the Super key. I believe this happens when another window is focused.
Wierdly enough, it only occurs on my laptop. I don't think it is an NVIDIA issue, since my main PC didn't have this bug even when the card was an RTX 2060. The one in my laptop is an RTX 3050 Mobile. My desktop never had this issue, even on NVIDIA.
I believe that this is an issue related to focus, but I'm likely wrong.
How should I debug this issue further in order to fix it? Fuzzel can output info logs if necessary. I can add any dmesg or hyprland logs from a clean boot if that would be useful.
Thankyou!
Beta Was this translation helpful? Give feedback.
All reactions