I am on elementaryOS (which is based on Ubuntu 16.04.3 LTS). After latest kernel update, key repeat stopped working. I mean the behaviour which types 'ffffffff' when I hold the 'f' key. I discovered, using xev, that my system is registering key presses constantly, even when I do not press, move or touch anything at all. I am also not able to login into a tty, because it types in '^@' into my login and password every second or so. xev reports this event:

KeyPress event, serial 37, synthetic NO, window 0x3e00001,
root 0x2c8, subw 0x0, time 161832, (322,168), root:(1193,635),
state 0x0, keycode 221 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes: 
XmbLookupString gives 0 bytes: 
XFilterEvent returns: False

I tried suggested solutions in a similiar post, but nothing helped. Any clues?

  • Seems like a stuck key. WD-40 – Rui F Ribeiro Jan 11 '18 at 11:51
  • I do not see anything stuck, and WD-40 is not available in my country, as I live in the Czech republic, Europe. – Daniel Zvir Jan 11 '18 at 13:52
  • I can get WD-40 here in Portugal...or something similar. – Rui F Ribeiro Jan 11 '18 at 13:53
  • I'll look into the alternatives. Meanwhile, any way to detect which key is being stuck? What is the 221 keycode? It even says NoSymbol. If I type the 'f' letter for example, it prints it directly into the output, that I pushed the 'f' letter. – Daniel Zvir Jan 11 '18 at 13:55
  • 221 it should be ] } – Rui F Ribeiro Jan 11 '18 at 14:05

It seems to be caused by a bug in the kernel module peaq_wmi as unloading it fixes the issue. This bug was intruced by the 4.13 kernel update. More people have had it. More info here: Arch linux forum, and the solution is here: unix & linux autorepeat does not work.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.