This bug is because of kernel upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=52471
All the info is in that bug report, including 2 patches to fix it. In short form, the (doomed to fail by timeout) battery status reporting injects a 5 second delay in keyboard device removal. Due to races in the kernel bluetooth code, this leads the code to remove devices from sysfs in the wrong order. This in turn leads to udev events being sent out with truncated device paths. This in turn causes Xorg evdev to receive the 'remove' events, but ignore them because they cannot match them up. When the keyboard re-connects, Xorg then sees the 'add' events matching a keyboard it thinks it already has, so ignores them ... so your keyboard doesn't work (or mouse too, if bluetooth as well!). IMHO This is NOT a problem in Xorg - it is a kernel issue leading to faulty udev events. Note the Google Chrome people patched their Xorg to work around the issue ... but the real fix should be in the kernel. ** Bug watch added: Linux Kernel Bug Tracker #52471 http://bugzilla.kernel.org/show_bug.cgi?id=52471 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075478 Title: bluetooth keyboards and mice not working after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/1075478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
