Skip to content

[Bug] Key-up reports lost when Linux USB autosuspend is enabled (stuck/repeating keys) #58

Open

Description

@conlanpatrek

Describe the Bug

Random keys (Backspace, Enter, letters) get stuck after being released and auto-repeat
indefinitely. The repeat stops only when any other key is pressed. Frequency: every
few minutes during normal typing.

/sys/bus/usb/devices/<keyboard>/power/control was auto (USB autosuspend enabled).
The key-up report is lost when the device suspends after a key is released. The next
keypress wakes the device and sends a full-state report, which implicitly releases the
stuck key.

libinput trace (libinput debug-events), Enter release arriving with the next keypress:

+337.528s  KEY_ENTER (28) pressed
           [~5.5s, no keyboard events; touchpad in use]
+343.026s  KEY_LEFTMETA (125) pressed
+343.026s  KEY_ENTER (28) released   <- same timestamp

The touchpad (i2c) kept reporting throughout; only the USB keyboard went silent.

Expected: the keyboard should survive USB suspend/resume without losing a key-up:
either resend the current key state after wakeup, or not allow suspend while a report
is pending or a key is held.

Keyboard Used

framework/ansi - Laptop 16 Keyboard Module ANSI (32ac:0012), stock firmware 0.3.1 via fwupd

Link to product page (if applicable)

https://frame.work/products/keyboard-module?v=FRAKEA00AA

Operating System

Fedora 44, kernel 7.2.5-200.fc44.x86_64, GNOME Shell 50.5 (Wayland)

qmk doctor Output

N/A — stock Framework firmware 0.3.1, not a custom build.

Is AutoHotKey / Karabiner installed

  • AutoHotKey (Windows)
  • Karabiner (macOS)

Other keyboard-related software installed

None

Additional Context

Hardware: Framework Laptop 16, AMD Ryzen AI 9 HX 370.

Possible workaround: disabling autosuspend for the keyboard appears to stop the
problem (still testing):

ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="32ac", ATTR{power/control}="on"

This only masks the bug and gives up the power savings from autosuspend.

Long-running community thread with the same symptom and workaround:
https://community.frame.work/t/solved-keys-stick-and-repeat-after-being-released/51153

Activity

  1. conlanpatrek commented on Oct 4, 2026

    @conlanpatrek
    Author

    It looks like upstream no longer has this bug, so this is probably resolved by #49

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions