Launchpad has imported 15 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=811534.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2012-04-11T11:00:10+00:00 James wrote: Created attachment 576744 Xorg.0.log from problem session Description of problem: After a suspend/resume cycle, X no longer recognises my Bluetooth mouse. - There's a confounding issue in that sometimes the Bt subsystem doesn't come back properly, see Bug 727106. Devices reappear after restarting the bluetooth service. - Following this, the mouse appears in the devices list in Gnome Shell, and other devices (e.g. file transfer from phone) works properly. - Upon reconnecting the mouse, messages like (WW) evdev: Bluetooth Mouse: device file is duplicate. Ignoring. appear in the Xorg logs (attached). Sometimes waiting for a few hours and then trying again works. I don't know if this is strictly an evdev bug. Might be udev or bluez or kernel or ... please reassign as appropriate. Version-Release number of selected component (if applicable): xorg-x11-drv-evdev-2.6.99.901-7.20120118git9d9c9870c.fc16.x86_64 udev-173-3.fc16.x86_64 bluez-4.96-3.fc16.x86_64 kernel-3.3.0-8.fc16.x86_64 kernel-3.3.1-2.fc16.x86_64 kernel-3.3.1-3.fc16.x86_64 xorg-x11-server-Xorg-1.11.4-3.fc16.x86_64 How reproducible: Intermittent, but frequent. Steps to Reproduce: 1. Suspend then resume. 2. Restart bluetooth.service if necessary, according to Bug 727106. 3. Reconnect Bluetooth mouse. Actual results: Mouse doesn't work. Expected results: Mouse works. Additional info: Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/0 ------------------------------------------------------------------------ On 2012-04-20T01:38:27+00:00 Peter wrote: *** Bug 811681 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/1 ------------------------------------------------------------------------ On 2012-04-20T02:31:11+00:00 Peter wrote: Either server or udev bug. The last parts of the log show that we get the "device added" event, but we never saw the "device removed" for it. The config_info string changes, so we don't automatically remove the previous instance when the new one is added. Lennart, any comments? Is there some race condition that we may suffer from in the server that we don't see the device removed event? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/2 ------------------------------------------------------------------------ On 2012-08-27T21:29:57+00:00 Dan wrote: Are there any workarounds known, besides restarting X? I don't particularly like having to shut down all programs to restart X. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/3 ------------------------------------------------------------------------ On 2012-08-27T21:49:57+00:00 Scott wrote: (In reply to comment #2) > Either server or udev bug. The last parts of the log show that we get the > "device added" event, but we never saw the "device removed" for it. > > The config_info string changes, so we don't automatically remove the > previous instance when the new one is added. > > Lennart, any comments? Is there some race condition that we may suffer from > in the server that we don't see the device removed event? Actually it's increasingly looking like a kernel bug - we're seeing the kernel netlink events with missing or corrupted components and also seeing other signs that pointers aren't going where they're supposed to... Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/4 ------------------------------------------------------------------------ On 2012-08-27T22:00:09+00:00 Pierre-Yves wrote: Dan, you might probably just unplug and re-plug the mouse Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/5 ------------------------------------------------------------------------ On 2012-08-27T22:26:09+00:00 Dan wrote: Pierre-Yves: I have internal bluetooth so there is no possibility to unplug anything. However, I have tried cycling power on the mouse and have tried running "systemctl restart bluetooth.service" without success. Restarting X (by logging out and back in) works though. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/6 ------------------------------------------------------------------------ On 2012-08-28T20:51:52+00:00 Andrew wrote: Scott is referring to the debugging we've been doing on Chromium OS. We have some more details in the bug: http://code.google.com/p/chromium- os/issues/detail?id=33813 It's looking like a race condition in the kernel. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/7 ------------------------------------------------------------------------ On 2012-09-12T13:59:24+00:00 Dan wrote: It is possible that this bug may not be related to bluetooth. I also have the same problem with a USB mouse. Unplugging and plugging back in doesn't fix the problem. This happens sometimes (well, once so far) when resuming from sleep. [603892.207] (II) config/udev: Adding input device PIXART USB OPTICAL MOUSE (/dev/input/mouse2) [603892.207] (II) No input driver specified, ignoring this device. [603892.207] (II) This device may have been added with another device file. [603892.209] (II) config/udev: Adding input device PIXART USB OPTICAL MOUSE (/dev/input/event12) [603892.209] (**) PIXART USB OPTICAL MOUSE: Applying InputClass "evdev pointer catchall" [603892.209] (II) Using input driver 'evdev' for 'PIXART USB OPTICAL MOUSE' [603892.209] (**) PIXART USB OPTICAL MOUSE: always reports core events [603892.209] (**) evdev: PIXART USB OPTICAL MOUSE: Device: "/dev/input/event12" [603892.209] (WW) evdev: PIXART USB OPTICAL MOUSE: device file is duplicate. Ignoring. [603892.227] (EE) PreInit returned 8 for "PIXART USB OPTICAL MOUSE" [603892.227] (II) UnloadModule: "evdev" Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/8 ------------------------------------------------------------------------ On 2012-10-08T23:27:42+00:00 Peter wrote: did you see a remove event for this device before event12 was added again? can't tell that from the log excerpt you posted, please always provide the full log. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/9 ------------------------------------------------------------------------ On 2012-10-13T10:02:16+00:00 kpijarski wrote: I'm having the same problem with apple magic mouse, very frustrating... Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/10 ------------------------------------------------------------------------ On 2012-10-13T10:04:55+00:00 kpijarski wrote: this is what dmesg gives me: [ 8307.249323] power_supply hid-B8:F6:B1:1D:C8:F0-battery: driver failed to report `capacity' property: -5 [ 8311.915977] magicmouse 0005:05AC:030D.0007: unknown main item tag 0x0 [ 8311.922708] power_supply hid-B8:F6:B1:1D:C8:F0-battery: driver failed to report `capacity' property: -5 [ 8311.922916] input: Anthony’s Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/bluetooth/hci0/hci0:34/input18 [ 8311.923976] magicmouse 0005:05AC:030D.0007: input,hidraw0: BLUETOOTH HID v3.06 Mouse [Anthony’s Mouse] on 68:5D:43:20:DD:33 [ 8312.053764] traps: upowerd[3633] trap int3 ip:3cdee4e991 sp:7fffdb032dc0 error:0 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/11 ------------------------------------------------------------------------ On 2012-10-13T14:00:46+00:00 Dan wrote: Created attachment 626561 another problem session As requested by Peter, a full log of a problem session. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/12 ------------------------------------------------------------------------ On 2012-10-17T04:00:48+00:00 kpijarski wrote: I don't know if this helps, but I have found a way to have the mouse back after suspend (but you need to have a second pointer to do that!): before suspend, I have to turn off bluetooth (without turning it off my computer would randomly not suspend at all. anyway, without turning it off there is no chance to have the mouse back after wakeup), and after wakeup I need to turn it on in gnome-shell first, and then cycle the hardware button (disable, and then re-enable BT) to have BT with mouse back. Just cycling the hardware button does NOT work. I think there is something very wrong with the bluetooth drivers in the current kernel (3.6.1 here)! I even had kernel panics after wakeup with bluetooth enabled. For me this is a new thing as I've never actually used BT and always turned it off on startup by default to save battery life, but now that I have a bluetooth mouse I seem to have been thrown back six years in terms of linux useability. Any idea what to do with this? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/13 ------------------------------------------------------------------------ On 2013-02-14T02:11:44+00:00 Fedora wrote: Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/26 ** Changed in: evdev Status: Unknown => Won't Fix ** Changed in: evdev Importance: Unknown => Undecided ** Bug watch added: code.google.com/p/chromium-os/issues #33813 http://code.google.com/p/chromium-os/issues/detail?id=33813 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1075478 Title: [HP EliteBook 8530w] Bluetooth keyboards and mice not working after suspend/resume Status in xserver-xorg-input-evdev: Won't Fix Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
