Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#24494 - Why is /lib/udev/rules.d/70-hid2hci.rules gone ?

Attached to Project: Arch Linux
Opened by Christophe (tolgam) - Sunday, 29 May 2011, 10:41 GMT
Last edited by Tom Gundersen (tomegun) - Monday, 30 May 2011, 18:43 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Andrea Scarpino (BaSh)
Tom Gundersen (tomegun)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
/lib/udev/rules.d/70-hid2hci.rules has been removed from the lastest version of the udev package.
In order to get my bluetooth back to work, I had to copy the final from an other machine I didn't upgraded yet.

Additional info:
* udev 171-1


Steps to reproduce:
This task depends upon

Closed by  Tom Gundersen (tomegun)
Monday, 30 May 2011, 18:43 GMT
Reason for closing:  Fixed
Comment by Ionut Biru (wonder) - Sunday, 29 May 2011, 10:58 GMT
http://git.kernel.org/?p=linux/hotplug/udev.git;a=commit;h=07f1d2860e8ee393abaaead75a6ab3af0f10efbb

as you see, it was moved to bluez. I guess we need to expect a new version soon
Comment by Ionut Biru (wonder) - Sunday, 29 May 2011, 11:00 GMT
in fact it should be available in the version released but our bluez is poorly packaged.

http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=94b0a8f405a591e6b082589e3f06ec9db747af31
Comment by Tom Gundersen (tomegun) - Sunday, 29 May 2011, 11:03 GMT
Hmm... Thanks for your report. It was moved to bluez upstream.

However, it was not include in our bluez package (this is my fault). I requested the old udev rules to be disabled from bluez (they create problems), but now that the hid2hci rule was moved to bluez this is also disabled by the same config switch. This we don't want.

In ideal situation would be to just disable the rule that enables autostart of bluez from udev, but to enable everything else. I don't know what is the best way to achieve this. Andrea?

[Actually, the best way would be to submit a patch upstream, as the autostart from udev is never the right thing to do.]
Comment by Andrea Scarpino (BaSh) - Sunday, 29 May 2011, 11:13 GMT
@Ioni, please next time check our logs:
http://projects.archlinux.org/svntogit/packages.git/commit/bluez/trunk?id=e87d23997f7fa993fa486dcbf549293a0687e939
http://projects.archlinux.org/svntogit/packages.git/commit/bluez/trunk?id=a0cf3b296449902915384f08c694891e64dcd437

@Tom,
I think that's the right way: enable everything and remove the rule which autostart bluez from udev.
Comment by Tom Gundersen (tomegun) - Sunday, 29 May 2011, 11:17 GMT
@Andrea: I think you are right. (I have on my ever-growing TODO to poke upstream about this, but I don't know if I'll ever get to it ;-) )
Comment by Andrea Scarpino (BaSh) - Sunday, 29 May 2011, 12:01 GMT
re-added in bluez 4.93-2

Loading...