Input issues with keyboard
Hi, I installed a fresh image of bazzite a day ago, and since then, I have been getting input issues with my keyboard (wired), where it skips some inputs, including key releases(so keys randomly stay pressed).
This issue seems to be specific to this keyboard, as I can't reproduce it with another keyboard (although, it may be because this keyboard is capable of registering the simultaneous inputs, while the other is not)
I can't, however, reproduce it on a fedora sway atomic install. This isn't DE specific, I also tried layering on niri instead of gnome, and the problem persisted
54 Replies
I can also add that the skipped inputs dissapear in
libinput debug-events, and I can only create this issue when pressing modifier keysfwiw, I've been having an issue with my keyboard since the 715 update. I rolled back to the 712 image and the keyboard worked fine. the only thing affected for me was the use of the HYPR key. you on a QMK keyboard by chance?
i am just confused at this point, it never happened before, but now I can reproduce it on a clean install of fedora silverblue, but not on another laptop, WITH THE SAME KEYBOARD, with a clean install of fedora silverblue
what kind of keyboard do you have? is it just CTRL, SHIFT, ALT, etc.?
Yeah, it's a pretty standard 10 keyless, I also have a qmk macro pad that has 0 issues
So this doesn't happen on a clean install of silver blue, but it happens on anything ublue related
And rebasing back to fedora silver blue doesn't fix it once it starts happening
Is there a way to try an older version, considering I never had this installed?
there is, but I would want to be sure that we're not creating more problems than we're helping by trying. I'm not a dev and not really an expert, but I have tried using different versions. there's a rollback helper that ought to let you pick different images that are still available online: https://docs.bazzite.gg/Installing_and_Managing_Software/Updates_Rollbacks_and_Rebasing/bazzite_rollback_helper/
Bazzite Rollback Helper - Bazzite Documentation
Bazzite is a custom image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices.
lemme ask around in the main chat and see if I can get advice on the best way to do this.
okay, so you want to follow instructions for rebasing here, but you need to make sure you are sticking to a different version of the same desktop environment. do not under any circumstances rebase from GNOME to KDE or vice versa. look at the list that the rollback helper offers and try something like the image ending with 0712 (stable).
that image works just fine for me. not sure if you and I are having the same problem, but that will at least give us some more info
thanks god this is a known issue, I was sooo frustrated
almost all time high
as booper said 712 seems to be fine
you should first type
it will give you a list of version you can rollback to
and then, if possible
I makred my initial report as solved so it's not a duplicate
A rollback won't work, this issue doesn't get removed by rebases, even going back to fedora silverblue, which doesn't have the issue, does solve it.
I would need an iso for an old version
you tried and it didn't work or you didn't try ?
I haven't tried, and I will, but I don't think it will work, and more importantly, even if those versions fix the issue, I don't think it will work
yeah, it does work
sorry i suppose
np
but we still need to fill a report I think
im suprised that this works, but rebasing to silverblue, which works as a clean install, didn't
maybe something from bazzite stays if you go back to silverblue
maybe the issue comes from fedora in the first place
and the version you use for silverblue is too new
nope, my laptop has been on silverblue for a while
and the fact that I go back to the latest silverblue version
then idk
🤷
who wants to open an issue on github ?
with all the informations we have
I can do that
I think there are at least 10ish users affected by this
any many more won't have noticed
in my case it's mild enough that I initially thought it was a hardware issue
yeah same
I could still type but some inputs didn't register and some keys still hold
yeah, I'll do the report in bazzite, it's got a nicer template for bugs
so that's probably the perfered spot
ty
I'll follow this actively because otherwise I can't update for a while
ill quickly check if it's fixed on unstable
can you try unstable?
0720 is still broken for me, but the unstable channel fixes it
which one
i just did bazzite-gnome:unstable
didn't specify
I don't have further than 720
but I don't use gnome
I'm on KDE
then it's bazzite:unstable
bazzite-rollback-helper list all
I try rn
you were right
so to summarize
stable 712 : ok
stable 715 : not ok
unstable 42.20250620.2 : ok
well then I'll wait until the next stable release to make a bug report
it'll probably be fixed by then
oh wait
it's 0620
not 0720
they haven't updated unstable for a while it seems
oh
you mean 620 is older than 712 ?
🤡
so yeah make sens it doesn't have the issue
I took the newest one from this list
yeah
im also on 0620
i think they just stopped doing unstable
but there is also "testing" 719
testing 719 will be older than stable 0720
how do you know
this versioning doesn't make any sens tbh
at least for non iniated
because it's the date
0720 is the 20th of july release
so 0719 was probably the testing release for 0720
just saw you open an issue
https://github.com/ublue-os/bazzite/issues/2946
if someone is searching for help
I hope it will get fixed eventually
GitHub
Input issues with keyboard · Issue #2946 · ublue-os/bazzite
Describe the bug When attempting to type with a keyboard, some inputs (either releasing or pressing events) are not registered. This can lead to missed inputs or keys staying pressed. Simultaneous ...
More info here if it helps: https://discord.com/channels/1072614816579063828/1395070461683044553
Woops just saw GitHub link. Will post my info there in a bit.
I've tried updating to latest testing-42.20250724.4
still not working as intended
I don't know what else we can do, is there any way to help with further investigating ?
keyboard is kinda essential to any OS...
try rebasing to
bazzite-rollback-helper rebase bazzite:testing-42.20250713
This is the first testing image after bazzite 0712, It causes the issue for me. Can you confirm you also have it?
libinput 1.28.1-1.fc42 -> 1.28.901-1.fc42
libinput-utils 1.28.1-1.fc42 -> 1.28.901-1.fc42
I think I found the cause, this version of libinput is not shipped by fedora, it's the first release candidate for libinput, so is also less stable
https://gitlab.freedesktop.org/libinput/libinput/-/issues/1156
This issue may potentially solve it, so I'll wait for the fix to be merged, and then make a bug report if that fixes it
and can you run sudo libinput list-devices for me?I think we already confirm that after 712 was the issue ? stable, unstable, and testing release
what part of the output do you want ?
your keyboard mostly
or send the entire output as a .txt file so I can add it to a bug report
ideally
hope there is nothing sensitive in it 😔
thanks, nothing personal unless you care about your power button's privacy
i'll post it only if need be
I have no idea, but I would guess that for things such as key logger, you probably want to know which ID is the keyboard
but yeah feel free to post it anywhere where its helpful
I'll add it here
the ID gets reset every boot
thanks man. i have this issue that i can't press 4 key simultaneously and the button stuck very often. i just installed bazzite this week so tbh i immediatelly pissed off and almost remove bazzite from my system. because i mainly play rhythm game, so this is a real deal breaker.
and then decide to search whats going on and saw someone post on fedora forum for having similar issue and fixed it by downgrading the libinput with dnf command.
now my issue fixed by downgrading to stable 0706 build (deck). it's look like bazzite team not doing proper test before pushing things to stable channel. hope they fix it soon because i dun want to keep using old build.
now my issue fixed by downgrading to stable 0706 build (deck). it's look like bazzite team not doing proper test before pushing things to stable channel. hope they fix it soon because i dun want to keep using old build.
@Perseid @HG https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/1282
The next release of libinput should fix thise issue
and no, this is fedora not testing thing, if you want to blame anyone
and it's a niche hardware thing, it happens, especially on a libinput RC
I don't want to blame anyone, lots of devs are giving away free time to develop these project
thank you for reporting that to us !
Solution
@HG 42.20250804 fixes this issue, you can update now
thank you, I was also watching at the bazzite release page, waiting for that 1.29.0-1