FS#25356 - [udev] 173-2 breaks bluetooth mouse usage

Attached to Project: Arch Linux
Opened by David Hoyes (dphoyes) - Monday, 01 August 2011, 23:04 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 02 August 2011, 18:33 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Andrea Scarpino (BaSh)
Tom Gundersen (tomegun)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Although the mouse can still be seen to connect via bluetooth, X no longer responds to it in any way. Downgrading to udev 172-2 returns all functionality.


Additional info:
udev 173-2
bluez 4.96-1
xorg-server 1.10.3-2
linux 3.0-2

Steps to reproduce: Upgrade to udev 173-2, restart the bluetooth daemon, and attempt to connect and use a bluetooth mouse using either blueman or gnome3's bluetooth utility.
This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 02 August 2011, 18:33 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in udev 173-3.
Comment by Tom Gundersen (tomegun) - Tuesday, 02 August 2011, 11:03 GMT
Thomas just posted the attached patch to the udev mailinglist. Please test if it fixes the problem for you.
   bluetooth.patch (2.6 KiB)
Comment by Thomas Bächler (brain0) - Tuesday, 02 August 2011, 11:19 GMT
Reference to the mailing list post: http://www.spinics.net/lists/hotplug/msg05034.html

This is the commit that broke it: http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=c49df20758e0f22778cfc93b598f2929f4c86272
The commit message is a bit short, but this is what I figured out: The /dev/input/{by-path,by-id} symlinks only refer to the USB bluetooth hci, not to the bluetooth device itself, leading to broken symlinks when you attach more than one bluetooth HID to the same bluetooth hci. Kay probably didn't realize the input_id data is used elsewhere than only in the persistent input rules. Let's hope he accepts the patch as it is.
Comment by Thomas Bächler (brain0) - Tuesday, 02 August 2011, 11:20 GMT
Forgot to say: Of course, the attached patch solves the problem on my end. I am pretty sure the reporter's problem will be solved as well.
Comment by Tom Gundersen (tomegun) - Tuesday, 02 August 2011, 11:24 GMT
@brain0: having looked over your patch it seems obviously correct. I'm tempted to push it to testing without waiting for Kay, as he is travelling this week. If for some reason it is rejected and a different fix is used instead we can update later on. What do you think?
Comment by Thomas Bächler (brain0) - Tuesday, 02 August 2011, 11:35 GMT
I'm happy either way, now that I already spent an hour figuring out what the problem was. If you like, go ahead.
Comment by Borromini (Borromini) - Tuesday, 02 August 2011, 11:36 GMT
I can confirm rebuilding udev from [testing] with Thomas's patch works fine. Both my bluetooth keyboard and mouse are functional again.

Thank you!
Comment by Tom Gundersen (tomegun) - Tuesday, 02 August 2011, 11:41 GMT
Pushed to [testing]. Thanks to everyone for using testing and reporting, so this time we caught the regression before it went to [core] :)
Comment by David Hoyes (dphoyes) - Tuesday, 02 August 2011, 11:54 GMT
The patch works. Thank you!

Loading...