Public bug reported:
Linux kernels after 3.2 introduced battery status reporting for devices
such as bluetooth keyboards and mouse.
Unfortunately there is an issue when such input devices are removed:
- a battery status report is requested
- this fails, because the device is being removed (communications with it are
now down)
- the failure results in a 5 second wait (the code has a 5 second timeout)
- the bluetooth hci code has a race condition: the 5 second delay means one
thread definitely loses the race
- the race condition leads to devices in the sysfs tree being removed in the
wrong order
- this leads to udev events being sent out with 'truncated paths'
- this leads to userspace programs like Xorg evdev ignoring the event, but then
getting confused about what keyboard/mice are actually attached
- this results in bluetooth keyboard/mice not working after a suspend/resume
(because on resume the input devices are first removed, and then re-added)
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117608
Title:
bluetooth incorrectly removes input devices
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1117608/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
