[Bug 732831] New: Logitech Bluetooth Keyboard diNovo Edge not working
https://bugzilla.novell.com/show_bug.cgi?id=732831 https://bugzilla.novell.com/show_bug.cgi?id=732831#c0 Summary: Logitech Bluetooth Keyboard diNovo Edge not working Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers@suse.de ReportedBy: rainer@fischer-nolte.de QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 after upgrading from openSUSE 11.4 to 12.1 my diNovo Edge keyboard doesn't work anymore. As soon as I enter a key BlueDevil comes up with "Logitech diNovo Edge is requesting access to this computer". Clicking "Trust and Authorize" with a separate cable mouse doesn't solve the problem, either. The keyboard is recognized and works while booting. Reproducible: Always Steps to Reproduce: 1. start computer 2. type a key 3. BlueDevil comes up Actual Results: no action Expected Results: normal keyboard (and integrated touchpad) use -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=732831 https://bugzilla.novell.com/show_bug.cgi?id=732831#c1 --- Comment #1 from Rainer Fischer <rainer@fischer-nolte.de> 2011-11-27 09:45:26 UTC --- workaround: in file /lib/udev/rules.d/97-bluetooth-hid2hci.rules search for # Logitech devices KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[34bc]", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" and replace "hiddev*" with "hidraw*" result: keyboard and touchpad work as expected. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=732831 https://bugzilla.novell.com/show_bug.cgi?id=732831#c Christian Trippe <ctrippe@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ctrippe@opensuse.org, | |seife@novell.slipkontur.de AssignedTo|kde-maintainers@suse.de |vbotka@suse.com -- 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.
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.
https://bugzilla.novell.com/show_bug.cgi?id=732831 https://bugzilla.novell.com/show_bug.cgi?id=732831#c3 David Walker <DHWalker@ucdavis.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |DHWalker@ucdavis.edu --- Comment #3 from David Walker <DHWalker@ucdavis.edu> 2011-11-28 04:18:25 UTC --- I think I'm having this same problem after upgrading to 12.1. Differences are that I'm running Gnome, and I have an Apple wireless keyboard on a Mac Mini, but I can't use the keyboard unless I reboot and re-pair. (In other words, the solution mentioned at the end of Comment #2 (pairing the keyboard) doesn't work. I have an Apple bluetooth mouse that does work, by the way. Please let me know if this doesn't look like the same problem. I can refile as a new bug, if that's the case. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=732831 https://bugzilla.novell.com/show_bug.cgi?id=732831#c4 Michele Cherici <contezero@technet.it> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |contezero@technet.it --- Comment #4 from Michele Cherici <contezero@technet.it> 2011-11-28 09:09:46 UTC --- I think it's a duplicate of Bug 681049 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=732831 https://bugzilla.novell.com/show_bug.cgi?id=732831#c5 Luke Tucker <luke_tucker@yahoo.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |luke_tucker@yahoo.co.uk --- Comment #5 from Luke Tucker <luke_tucker@yahoo.co.uk> 2011-12-13 22:43:58 UTC --- I would like to add that I have had a bit of trouble with this and xfce but I now have it working. What I have found is that you need to ignore the xfce authorisation window that pops up when you first start typing. This just doesn't work no matter what you try. I can provide a a detailed report of everything I tried there along with bluetoothd debug output if necessary but it's not really the same as this issue. If however, you use the icon in the bottom panel that links to the gnome 3 bluetooth app, you can pair the device manually. You have to keep pressing ctrl throughout the process because the keyboard switches itself off a few seconds after you stop typing. Once it was paired it also only started working properly after bluetoothd was restarted for some reason. Logs were reporting 'Operation in progress'. After that it now works fine even after a reboot and no re-pairing has been necessary. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=732831 https://bugzilla.novell.com/show_bug.cgi?id=732831#c6 --- Comment #6 from David Walker <dhwprof@gmail.com> 2011-12-16 17:14:52 UTC --- Restarting bluetoothd didn't work for me. I still have to re-pair the keyboard every time. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com