Sometimes loses input devices on suspend/resume: Device has changed - disabling.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
X.Org X server |
Fix Released
|
Medium
|
|||
xserver-xorg-input-evdev (Ubuntu) |
Fix Released
|
Medium
|
Steve Beattie |
Bug Description
Binary package hint: xserver-
On the way back from Berlin on Friday, I resumed my laptop on the plane to find that X was no longer accepting keyboard events. I tracked this down as far as EvdevCacheCompare having decided that the keyboard wasn't in the same state as it was on suspend and therefore disabling it. It's possible that this is related to bug 322946, but I don't know whether the position fields are defined for keyboard devices; unfortunately, my laptop ran out of battery before I could get it connected to a network, download debugging symbols, and attach gdb to the X server, which had been my plan.
I've attached all the information I gathered before running out of battery, in the hope that it will be helpful. I was running kernel version 2.6.28-6.17.
The error message was: (EE) AT Translated Set 2 keyboard: Device has changed - disabling.
Changed in xorg-server: | |
status: | Unknown → Confirmed |
description: | updated |
Changed in xorg-server: | |
status: | Confirmed → In Progress |
Changed in xserver-xorg-input-evdev (Ubuntu): | |
status: | Incomplete → Confirmed |
tags: |
added: jaunty regression-release removed: regression-potential |
Changed in xorg-server: | |
status: | In Progress → Fix Released |
Changed in xorg-server: | |
importance: | Unknown → Medium |
Changed in xorg-server: | |
importance: | Medium → Unknown |
Changed in xorg-server: | |
importance: | Unknown → Medium |
Created an attachment (id=22734)
Xorg.0.log
Forwarding this bug from a Ubuntu reporter: /bugs.edge. launchpad. net/ubuntu/ +source/ xserver- xorg-input- evdev/+ bug/327175
https:/
[Problem]
On resume, X no longer accepts keyboard events, due to EvdevCacheCompare determining keyboard is not in the same state as was on suspend, and thus disabling it.
[Original Report]
On the way back from Berlin on Friday, I resumed my laptop on the plane to find that X was no longer accepting keyboard events. I tracked this down as far as EvdevCacheCompare having decided that the keyboard wasn't in the same state as it was on suspend and therefore disabling it. It's possible that this is related to bug 322946, but I don't know whether the position fields are defined for keyboard devices; unfortunately, my laptop ran out of battery before I could get it connected to a network, download debugging symbols, and attach gdb to the X server, which had been my plan.
I've attached all the information I gathered before running out of battery, in the hope that it will be helpful. I was running kernel version 2.6.28-6.17.