Bug 2437571 - Keyboard broken upon resume
Summary: Keyboard broken upon resume
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Justin M. Forbes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-02-07 22:54 UTC by Ronald L Humble
Modified: 2026-02-07 22:54 UTC (History)
14 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
kernel.logs (88.73 KB, text/plain)
2026-02-07 22:54 UTC, Ronald L Humble
no flags Details

Description Ronald L Humble 2026-02-07 22:54:52 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.