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 Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/1075478

Title:
  bluetooth keyboards and mice not working after suspend/resume

Status in xserver-xorg-input-evdev:
  Unknown
Status in “xserver-xorg-input-evdev” package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 12.10 I encountered the following problem:

  I have my apple wireless bluetooth keyboard paired up to Ubuntu, and
  it works fine when I boot up my laptop (HP EliteBook 8530w) as soon as
  I hit the login screen. However, if I then suspend and resume my
  laptop again, the bluetooth keyboard does not respond anymore.
  According to the bluetooth GUI applet it is still succesfully paired
  up and connected, and I see the green light on my keyboard blinking a
  few times when I hit a key for the first time after resume which is
  also the case when it _does_ work, but I get no response whatsoever
  from Ubuntu when typing on my keyboard.

  "sudo service bluetooth restart" does not work.

  Please let me know what additional information to provide.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evdev/+bug/1075478/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to