7/15 update affected keyboard behavior?
Hi all,
I am using Bazzite 42.20250715 in GNOME Stable.
I've been using a QMK keyboard (connection via USB) for the last few months that utilizes a HYPR keypress for a handful of GNOME and nvim shortcuts (HYPR presses gui, alt, ctrl, and shift simultaneously).
Up until until the 7/15/2025 Bazzite update, that key worked for me as expected. For instance, pressing HYPR+C would center a window in the current workspace, HYPR+Y in nvim would highlight and yank code from one blank line to the next blank line, etc. These are all shortcuts I created myself using the tiling manager extension and my nvim config file.
But this morning, all of my HYPR key presses go unrecognized, no matter which program or shortcut I am trying to use. I checked that the key is functioning mechanically and was able to confirm it because it controls my volume on a different layer.
Pressing all four keys independently (holding down the gui, alt, ctrl, and shift keys instead of using hyper) works, so I am wondering if there is some kind of conflict in the 7/15 update that might be affecting the way keyboard keycodes are registered? FWIW, the
meh key still works just fine (that's alt+ctrl+shift). Maybe something is going on with the way the gui key is handled?
Also maybe relevant: I was able to confirm that, at least in bash, the HYPR key is sending four indepedent keypresses by using showkey. The output was as follows:
Is there anything I need to do with Bazzite to make HYPR work again? I checked with the QMK people and they seemed to think my board was setup correctly. Since it was working last night before the update, my assumption is the update to 7/15 from 7/12 is somehow responsible. Thanks for your help!7 Replies
just rolled back to the 7/12 image and can confirm that the hyper key works as expected
That's so odd that an update would change your keyboard around like that
Remember to pin the image before you try to update again!
the rest of the keyboard works fine, so I don't know how high priority this really is (and I don't think it's changing my keyboard at all), but I am curious if anything else might have been affected... guessing it has something to do with the way Wayland handles the gui keycode in specific, since meh works and hypr doesn't... maybe something got reassigned in the xkb setup? which I have zero clue how to manipulate
in case anyone else sees this, there is at least one other user reporting keyboard issues: https://discordapp.com/channels/1072614816579063828/1395356798336106526/1395356798336106526
updated to 7/18 image and no difference - rolling back to 7/12 still helps. waiting to hear back from other user in case the 7/12 image works for them too.
https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/1282 This should fix it
Oh wow it was in libinput. Would not have expected that. Thanks for submitting that ticket!
42.20250804 fixes this issue, you can update now
Nice, thank you!!