Since kernel 3.6 the udev rule for hid2hci doesn't work anymore. At least for devices from Logitech the name of the subsystem has to be changed from usb to usbmisc. So in the file /lib/udev/rules.d/97-bluetooth-hid2hci.rules from bluez-hid2hci(-4.99-2.fc17.x86_64) the following has to be changed: - SUBSYSTEM!="usb", GOTO="hid2hci_end" + SUBSYSTEM!="usbmisc", GOTO="hid2hci_end" I don't know if that is needed for the Dell devices too. The reason is the following commit in the mainline kernel: 7e97243c2080ecae7129e83635227fdebd4feef6 (USB: rename the usb misc class from "usb" to "usbmisc") Regards, Alexander
Using SUBSYSTEM!="usb*", GOTO="hid2hci_end" instead of SUBSYSTEM!="usbmisc", GOTO="hid2hci_end" in my proposal above should match the subsystem usb too, if that hasn't changed for Dell devices, so using "usb*" might be the better solution. It works here too using a dongle from Logitech.
Btw., using "usb*" instead of "usbmisc" would work with kernels < 3.6 too, so it looks like the right choice.
bluez-4.101-4.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/bluez-4.101-4.fc18
bluez-4.101-5.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/bluez-4.101-5.fc18
Package bluez-4.101-4.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing bluez-4.101-4.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-18715/bluez-4.101-4.fc18 then log in and leave karma (feedback).
bluez-4.101-5.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
bluez-4.101-6.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/bluez-4.101-6.fc18
bluez-4.101-6.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.