https://bugzilla.novell.com/show_bug.cgi?id=732831 https://bugzilla.novell.com/show_bug.cgi?id=732831#c2 --- Comment #2 from Stefan Seyfried <seife@novell.slipkontur.de> 2011-11-27 20:04:36 CET --- This is working as designed. By changing the rule, it will never get executed, and thus your BT dongle will not be placed into HCI mode, instead operating as a HID device. See the commit message of the commit that fixed that issue: commit 63c3e0561a616dd72f1b78fcd9fd5e88015f2b31 Author: Peter Hurley <peter@hurleysoftware.com> Date: Fri Jun 3 16:53:03 2011 -0400 Fix udev rule for Logitech devices The *real* history of this file is a nightmare. Now that it's back in the bluez project, fix the problems that were added while it was in udev. 1) Only hiddev* devices provide the ioctl interface hid2hci uses to switch from HID->HCI for --method=logitech-hid. (inquiring minds can look in the kernel git tree at drivers/hid/usbhid/hiddev.c) 2) hidraw* devices don't belong to subsystem=usb (they are subsystem=hidraw). This means that the udev rule that matched based on hidraw* would never have been run anyway because of the early-out subsystem!=usb on line 4. This fix is going to cause major regressions in distros because there is currently no way provided by bluez to *NOT* run hid2hci. Many, many users (and maintainers) mistakenly believe that because the keyboard and mouse works when the vid/pid of their device is matched by the hidraw* rule, that "bluetooth" must be working. Of course, what's really happening is the keyboard and mouse are working as HID input devices instead. Now this does not help you and your problem ;) If you don't intend to use any bluetooth devices (at least with this dongle you can't, because it will be in HID mode anyway), you can just remove that rule or uninstall all bluetooth related packages. Another solution would be to just pair the keyboard and then use it as a bluetooth keyboard. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.