On the current linux kernel /sys/class/bluetooth no longer contains a hci[0-9]* entry so the bluetooth hotplug fails. Changing the test to /sys/bus/bluetooth/devices/hci[0-9]* fixes the script and restores hotplug functionality. Reproducible: Always Steps to Reproduce: Insert or enable a bluetooth host device Actual Results: Nothing happens; bluetooth service fails to start Expected Results: Bluetooth service should be run through dbus hotplug when hci device becomes available
We don't have anything to do with bluetooth or udev.
(In reply to comment #1) > We don't have anything to do with bluetooth or udev. > "/lib(64)/udev/bluetooth.sh" belongs to net-wireless/bluez-utils-3.36 Script is Gentoo provided: "net-wireless/bluez/files/bluez-utils-3.10.1-udev.script"
(In reply to comment #2) > (In reply to comment #1) > > We don't have anything to do with bluetooth or udev. > > > > "/lib(64)/udev/bluetooth.sh" belongs to net-wireless/bluez-utils-3.36 > > Script is Gentoo provided: > "net-wireless/bluez/files/bluez-utils-3.10.1-udev.script" > Sorry, that should have been "net-wireless/bluez-utils/files/bluez-utils-3.10.1-udev.script"
emerge --info in attachment please. Also, define the "current kernel" for you. Please, reopen the bug, when you have submitted these information.
(In reply to comment #4) > emerge --info in attachment please. Also, define the "current kernel" for you. > Please, reopen the bug, when you have submitted these information. > At least Linus' 2.6.27-rc* kernels are showing this behaviour, I recently switched to btusb from hci_usb due to the broken suspend handling, it may be this is that has caused the change in behaviour. If so, it could also be the case with earlier kernels?
Created attachment 163033 [details] emerge --info output
Further info provided, please note, I did provide a fix in the bug description, although it does need testing on systems which do not currently show this bug.
doesn't block the security bug because 2.6.27 hasn't even been release
net-wireless/bluez already fixes this, then, it will be solved when it hits stable or fix is backported
This is solved then, ok with closing this?
Fixed with current stable bluez