On Wed, 19 Oct 2016 02:42:40 -0600 Trent Gamblin <trent@xxxxxxxxxx> wrote: > Source: linux > Severity: normal > > Dear Maintainer, > > I have a PC with a mouse connected by a Logitech Unifying Receiver, and > an Android TV box with a keyboard connected by a separate Unifying > Receiver. The keyboard shows up on the Linux box with a message in > dmesg: > > [ 3.120080] usb 5-2.1: new high-speed USB device number 5 using xhci_hcd > [ 3.124336] usb 5-1.2: New USB device found, idVendor=046d, idProduct=c52b > [ 3.124340] usb 5-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 > [ 3.124343] usb 5-1.2: Product: USB Receiver > [ 3.124345] usb 5-1.2: Manufacturer: Logitech > [ 3.136292] logitech-djreceiver 0003:046D:C52B.0004: hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:0e:00.0-1.2/input2 > [ 3.160384] usb 2-3: new SuperSpeed USB device number 3 using xhci_hcd > [ 3.190438] usb 2-3: device descriptor read/8, error -71 > [ 3.221096] usb 5-2.1: New USB device found, idVendor=03f0, idProduct=7317 > [ 3.221099] usb 5-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > [ 3.221102] usb 5-2.1: Product: HP LaserJet P3005 > [ 3.221104] usb 5-2.1: Manufacturer: Hewlett-Packard > [ 3.221106] usb 5-2.1: SerialNumber: CNR1N17173 > [ 3.266438] input: Logitech Performance MX as /devices/pci0000:00/0000:00:1c.4/0000:0e:00.0/usb5/5-1/5-1.2/5-1.2:1.2/0003:046D:C52B.0004/0003:046D:101A.0005/input/input3 > [ 3.266819] logitech-hidpp-device 0003:046D:101A.0005: input,hidraw2: USB HID v1.11 Mouse [Logitech Performance MX] on usb-0000:0e:00.0-1.2:1 > [ 3.272667] input: Logitech K400 Plus as /devices/pci0000:00/0000:00:1c.4/0000:0e:00.0/usb5/5-1/5-1.2/5-1.2:1.2/0003:046D:C52B.0004/0003:046D:404D.0006/input/input4 > [ 3.273252] logitech-hidpp-device 0003:046D:404D.0006: input,hidraw3: USB HID v1.11 Keyboard [Logitech K400 Plus] on usb-0000:0e:00.0-1.2:2 > > It also shows up in the battery applet in Mate. > > I think either the kernel or the applet should ignore it since it's not > plugged into the PC (it doesn't actually work BTW.) > > Problem exists in 4.7.0 and up to the latest kernel I could find which > was 4.8.0-rc8. Trent also stated that under Windows the keyboard is *not* shown as connected, so it seems the receiver does provide enough information to tell that it's not currently connected. Ben. -- Ben Hutchings I'm always amazed by the number of people who take up solipsism because they heard someone else explain it. - E*Borg on alt.fan.pratchett
Attachment:
signature.asc
Description: This is a digitally signed message part
