Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#13948 - [xf86-input-evdev] Internal ThinkPad keyboard stops responding after long time in KDE4
Attached to Project:
Arch Linux
Opened by Daniel Böhmer (dboehmer) - Tuesday, 24 March 2009, 23:43 GMT
Last edited by Aaron Griffin (phrakture) - Tuesday, 19 January 2010, 19:32 GMT
Opened by Daniel Böhmer (dboehmer) - Tuesday, 24 March 2009, 23:43 GMT
Last edited by Aaron Griffin (phrakture) - Tuesday, 19 January 2010, 19:32 GMT
|
DetailsDescription:
I run X.org with KDE4 on ThinkPad T61. After I spent some time in X my internal ThinkPad keyboard refuses key presses out of the sudden. If I connect an USB keyboard I can use it. Also the whole system still runs fine! Even without keyboard but with touchpad I can control the desktop and all apps work like they should. After restarting X keyboard works again. When switching to text terminal internal keyboard works, too. Following a hint in IRC I configured KDE4 to use special keyboard layouts. This disabled keyboard input at all. I could only type again after disabling keyboard layouts again and plugging in the USB keyboard another time. This bug has occured only few times during the last one or two weeks. But it is a major system "crash" because I cannot work well when on my way. There is no USB keyboard when I am in the train or something:-) Additional info: * output of "xev" when pressing 1st ABC on the USB keyboard and 2nd on the internal keyboard - http://rafb.net/p/ZTqrGi91.html Steps to reproduce: 1. start KDE4 on ThinkPad 2. work with the system for an unknown period of time 3. recognize you can't type anymore 4. connect USB keyboard and kill X with that;-) |
This task depends upon
Closed by Aaron Griffin (phrakture)
Tuesday, 19 January 2010, 19:32 GMT
Reason for closing: Deferred
Additional comments about closing: No response in 7 months
Tuesday, 19 January 2010, 19:32 GMT
Reason for closing: Deferred
Additional comments about closing: No response in 7 months
rmmod -f evdev; modprobe evdev
This is only a work-around!
Thank you for your reply!