Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 2128585 [details] kernel.logs 1. Please describe the problem:upon resume from suspend/hibernate keyboard was broken. KDE-rawhide image fully upgraded on February 4, 2026. 2. What is the Version-Release number of the kernel: kernel-6.19.0-0.rc8.54.fc44.x86_64 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : kernel-6.19.0-0.rc8.54.fc44.x86_64; No issues with Fedora /42/43. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: resume from hours long suspend/hibernate; keyboard broken. Reboot immediately reported 'Keyboard Failure'. Boot on other Fedora/other Linux OS and keyboard failure confirmed. [backspace] not as expected; most times, keyboard just not recognized. Suspend/hibernate not risked with an alternate working keyboard. Could be a coincidence, but timing curious if so. Reporting for completeness in case other cases of hardware failure reported. A virtual machine install. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: Not risking other hardware in a suspend/hibernate. 6. Are you running any modules that not shipped with directly Fedora's kernel?: no 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag.
This report has not received an update in over 90 days. If this issue is still relevant to you, please do not hesitate to update this report with any relevant details on recent investigative steps or changes and we will absolutely work to understand how to best move forward. Otherwise, this bug report will need to be closed in 30 days. No worries, however; should you need still assistance after the report is closed, please do not hesitate to create a new bug report referencing this report and with any new details on the matter. NOTE: This is an automated mass update.
Since this report was not updated over the past 30 days, it will be closed out as INSUFFICIENT_DATA. However, if this issue is still occurring and you are able to reproduce it, please do not hesitate to reopen this bug and update it with fresh instances of the same informaiton.