udev 97-hid2hci.rules missing usb id for logitech dinovo 2

Bug #1688663 reported by Jesús Diéguez Fernández
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Fix Released
Undecided
Konrad Zapałowicz

Bug Description

Trying to install kubuntu 16.04.2 (Xenial Xerus) today, the Logitech dinovo 2 bluetooth keyboard and mouse didn't work, nor in live cd nor after being installed using another keyboard and mouse.

In /lib/udev/rules.d/97-hid2hci.rules there are two lines for Logitech devices:

# Logitech devices
KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[3bc]", \
  RUN+="hid2hci --method=logitech-hid --devpath=%p"
# Logitech, Inc. diNovo Edge Keyboard
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c714", \
  RUN+="hid2hci --method=logitech-hid --devpath=%p"

lsusb shows in my computer:

Bus 001 Device 006: ID 046d:c704 Logitech, Inc. diNovo Wireless Desktop

The id is almost equal (c714 <> c704). After adding a new line with the missing id, the keyboard and mouse started to work:

# Logitech, Inc. diNovo 2
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c704", \
  RUN+="hid2hci --method=logitech-hid --devpath=%p"

I've also followed these other bugs to find out the file that I needed to modify and that my keyboard needs hidraw instead of hiddev:

https://bugs.launchpad.net/ubuntu/+source/udev/+bug/872940
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/123920

Revision history for this message
Jesús Diéguez Fernández (jesusdf) wrote :
Revision history for this message
Konrad Zapałowicz (kzapalowicz) wrote :

Interesting. Will look into this.

Changed in bluez (Ubuntu):
assignee: nobody → Konrad Zapałowicz (kzapalowicz)
tags: added: bluez-desktop
Revision history for this message
Konrad Zapałowicz (kzapalowicz) wrote :

@jesusdf

you have written that:

"the Logitech dinovo 2 bluetooth keyboard and mouse didn't work, nor in live cd nor after being installed using another keyboard and mouse."

I wonder - were you able to pair it or that did not work too?

tags: added: papercuts2017
Revision history for this message
Jesús Diéguez Fernández (jesusdf) wrote :

The keyboard is quite old, it has a technology prior to the Logitech Unifying, but probably this led to it. It has a dongle that it autopairs to it, so really you don't have to manually pair/configure it. For example, it works out of the box accessing the bios of the computer.

Revision history for this message
Jesús Diéguez Fernández (jesusdf) wrote :

Any news on this topic? Do you need any additional information?

Revision history for this message
Konrad Zapałowicz (kzapalowicz) wrote :

This shall be released

Changed in bluez (Ubuntu):
status: New → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Shall be or was released? :)

Revision history for this message
Konrad Zapałowicz (kzapalowicz) wrote :

Meaning that it is out :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.