Keyboard and Mouse unresponsive randomly during session
My keyboard and mouse become unresponsive at a random point during a session. Fixed on reboot, but then becomes unresponsive again at a random point.
This happens with external mice and keyboard (wired or BT), as well as the built-in laptop keyboard. The only thing that will work is my touchpad, which I can use to reboot the laptop.
This occurred after a recent update after not updating the system since the beginning of Feb.

27 Replies
adding it here too
Will need the whole log
sudo dmesg | fpaste
journalctl | fpaste
Add it here
If journalctl is too big write it to a file and upload elsewhere
journalctl > ~/journal.log
Should put it in your home folder so you can upload it, but try fpaste firstguessing journal was too big?
very much so
you got a file made at least of it from when it just happened?
perfect lets see
do you happen to have the estimated time it happened?
then i can skip to around that time in the log
10:35-10:45
guessing you rebooted then since i see a lot of services stopping
yeah nothing there from what i see
I restarted at 10:45 ish
hey @antheas when youre free, do you see anything that stands out here or anything else we can grab?
all i see in dmesg is the usb devices randomly disconnect π€
yeah i saw the shutdown π
maybe I will go back a bit in the log
Maybe it's the 6.13 USB bug people are talking about
oh boy 6.13 just keep on giving doesnt it :clueless:
heres a bit further of a look back
will give it a look, if i find nothing i can find you the newest image without kernel 6.13 and you can see if that still has the issue
@MrSujano run
rpm-ostree status
and take note of the version you have that is working
then bazzite-rollback-helper rebase 41.20250227
to go to the last version with kernel 6.12 and stay there (you will not get updates past this point unless you rebase back to stable).
to go back to the latest stable run bazzite-rollback-helper rebase stable
Will roll back to 6.12 - thanks!
this I think is one of my favourite features of Bazzite/Atomic. So easy to roll back without breaking stuff
yeah it is, i used it on my htpc back when it used RX570 as the gpu
was broken for the longest time in gamescope so i had to stay a whole fedora version behind for months π
Rolled back and everything seems fine now - thank you very, very much for your time and help!
run
sudo ostree admin pin 0
to pin the image, that way you can make sure you can keep that image if this takes a long time to fix.
but i suspect it might be the usb bug antheas mentioned so you can try rebasing back to stable after a period and see if the issue still happens, and then rollback with rpm-ostree rollback
if it still isnt fixedwill do, it's such a weird issue. Fortunately everything else is pretty rock solid
and you can unpin the image once its fixed with
sudo ostree admin pin --unpin 1
replace 1 with 2 if it says 1 is already unpinned
or you can just grab the index of the pinned image with rpm-ostree status -v
yeah at least you can lock yourself to a working image while kernel people figure out the issue πRevisiting this one - Interestingly, it turns out it was the discord app. Uninstalling the app and logging in through the web seems to have fixed the issue after updating the the latest stable bazzite.
completely bizzare
huh, thats a new one :clueless:
i love technology!
I'm absolutely baffled. Ah well, web browser discord is fine
let me baffle you some more then!
i had a windows application crash in my windows VM for the past 2 weeks because of a bug in the linux kernel :huh:
workaround for the time being is to add a kernel argument until the fix is merged upstream
maybe try discord canary?
its what we have to use for screenshare anyway atm
https://github.com/flathub/com.discordapp.DiscordCanary
GitHub
GitHub - flathub/com.discordapp.DiscordCanary
Contribute to flathub/com.discordapp.DiscordCanary development by creating an account on GitHub.
Will give it a shot - thanks!
AHAHAHAHA that's wild
yeah when someone told me the fix i was like "you cant be serious" and i tried it and the application didnt crash anymore π