Bug 823815

What information does udev have about the devices?:
udevadm info -q all -p /sys/devices/pci...

When plugged in directly (working normally):

P: /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.2/0003:046D:C52B.0016/input/input20
E: DEVPATH=/devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.2/0003:046D:C52B.0016/input/input20
E: EV=17
E: ID_BUS=usb
E: ID_FOR_SEAT=input-pci-0000_00_1d_0-usb-0_1_1_2
E: ID_INPUT=1
E: ID_INPUT_MOUSE=1
E: ID_MODEL=USB_Receiver
E: ID_MODEL_ENC=USB\x20Receiver
E: ID_MODEL_ID=c52b
E: ID_PATH=pci-0000:00:1d.0-usb-0:1:1.2
E: ID_PATH_TAG=pci-0000_00_1d_0-usb-0_1_1_2
E: ID_REVISION=1200
E: ID_SERIAL=Logitech_USB_Receiver
E: ID_TYPE=hid
E: ID_USB_DRIVER=usbhid
E: ID_USB_INTERFACES=:030101:030102:030000:
E: ID_USB_INTERFACE_NUM=02
E: ID_VENDOR=Logitech
E: ID_VENDOR_ENC=Logitech
E: ID_VENDOR_ID=046d
E: KEY=ffff0000 0 0 0 0
E: MODALIAS=input:b0003v046DpC52Be0111-e0,1,2,4,k110,111,112,113,114,115,116,117,118,119,11A,11B,11C,11D,11E,11F,r0,1,6,8,am4,lsfw
E: MSC=10
E: NAME="Logitech Unifying Device. Wireless PID:101b"
E: PHYS="usb-0000:00:1d.0-1:1"
E: PRODUCT=3/46d/c52b/111
E: PROP=0
E: REL=143
E: SUBSYSTEM=input
E: TAGS=:seat:
E: UNIQ=""
E: USEC_INITIALIZED=6761346382

When plugged in via the USB hub:

P: /devices/pci0000:00/0000:00:1a.7/usb1/1-6/1-6.3/1-6.3:1.2/0003:046D:C52B.001E/input/input22
E: DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb1/1-6/1-6.3/1-6.3:1.2/0003:046D:C52B.001E/input/input22
E: EV=17
E: ID_BUS=usb
E: ID_FOR_SEAT=input-pci-0000_00_1a_7-usb-0_6_3_1_2
E: ID_INPUT=1
E: ID_INPUT_MOUSE=1
E: ID_MODEL=USB_Receiver
E: ID_MODEL_ENC=USB\x20Receiver
E: ID_MODEL_ID=c52b
E: ID_PATH=pci-0000:00:1a.7-usb-0:6.3:1.2
E: ID_PATH_TAG=pci-0000_00_1a_7-usb-0_6_3_1_2
E: ID_REVISION=1200
E: ID_SEAT=seat-usb-pci-0000_00_1a_7-usb-0_6
E: ID_SERIAL=Logitech_USB_Receiver
E: ID_TYPE=hid
E: ID_USB_DRIVER=usbhid
E: ID_USB_INTERFACES=:030101:030102:030000:
E: ID_USB_INTERFACE_NUM=02
E: ID_VENDOR=Logitech
E: ID_VENDOR_ENC=Logitech
E: ID_VENDOR_ID=046d
E: KEY=ffff0000 0 0 0 0
E: MODALIAS=input:b0003v046DpC52Be0111-e0,1,2,4,k110,111,112,113,114,115,116,117,118,119,11A,11B,11C,11D,11E,11F,r0,1,6,8,am4,lsfw
E: MSC=10
E: NAME="Logitech Unifying Device. Wireless PID:101b"
E: PHYS="usb-0000:00:1a.7-6.3:1"
E: PRODUCT=3/46d/c52b/111
E: PROP=0
E: REL=143
E: SUBSYSTEM=input
E: TAGS=:seat:seat-usb-pci-0000_00_1a_7-usb-0_6:
E: UNIQ=""
E: USEC_INITIALIZED=6825458265

I'm guessing that seat-usb-pci-0000_00_1a_7-usb-0_6 is not right...

Do you have any seat rules under /etc?:
grep SEAT /etc/udev/rules.d/*

No, there is nothing under /etc/udev/rules.d at all (apart from the rules which are evidently created by systemd-loginctl attach, which I have been removing for testing this bug). I haven't customised any configuration related to systemd or udev on this box, apart from enabling/disabling various services.

Please attach the output of
udevadm info --export-db

What is the vendor/product id of the USB hub you connect this to? Can you please provide the lsusb output?

My educated guess is that the current check for MIMO USB displays is a bit too broad since it uses a generic VID/PID for the hub that is built in (058f:6254). We should make this a bit more specific.

Good guess Lennart :-)

$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 058f:6254 Alcor Micro Corp. USB Hub
Bus 006 Device 002: ID f617:0905  
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver

"Alcor Micro Corp. USB Hub" is the hub (it's actually inside my Samsung monitor).

I commented out this line in /lib/udev/rules.d/71-seat.rules:

# Mimo 720, with integrated USB hub, displaylink graphics, and e2i touchscreen
#SUBSYSTEM=="usb", ATTR{idVendor}=="058f", ATTR{idProduct}=="6254", ENV{ID_AUTOSEAT}="1"

and now everything is working nicely.

Fixed in git.

systemd-44-13.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/systemd-44-13.fc17

Package systemd-44-14.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-44-14.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-9471/systemd-44-14.fc17
then log in and leave karma (feedback).

systemd-44-14.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

hello,

i have no idea if my issue is related to this one but this was the only bug that is analogous to mine that i could find: the thing is, i have all the above updates installed (i just got a new computer, so the system is fresh), so my wireless logitech mouse works with a hub, but it does not work *without* a hub anymore. is it possible that this is connected to the above? (all the ports are usb 3.0, but the hub is usb 2.0.)

dmesg when plugged directly into the computer (dell inspiron 7520):

[ 5106.901515] usb 3-4: new full-speed USB device number 14 using xhci_hcd
[ 5106.915115] usb 3-4: New USB device found, idVendor=046d, idProduct=c52b
[ 5106.915121] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 5106.915124] usb 3-4: Product: USB Receiver
[ 5106.915126] usb 3-4: Manufacturer: Logitech
[ 5106.918268] logitech-djreceiver 0003:046D:C52B.0020: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-4/input2
[ 5106.918534] logitech-djreceiver 0003:046D:C52B.0020: logi_dj_probe:logi_dj_recv_query_paired_devices error:-32
[ 5106.918747] logitech-djreceiver: probe of 0003:046D:C52B.0020 failed with error -32

dmesg when plugged into the hub:

[ 5356.068340] usb 3-1.1: new full-speed USB device number 15 using xhci_hcd
[ 5356.082123] usb 3-1.1: New USB device found, idVendor=046d, idProduct=c52b
[ 5356.082128] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 5356.082142] usb 3-1.1: Product: USB Receiver
[ 5356.082144] usb 3-1.1: Manufacturer: Logitech
[ 5356.085787] logitech-djreceiver 0003:046D:C52B.0023: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-1.1/input2
[ 5356.088998] input: Logitech Unifying Device. Wireless PID:101d as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1.1/3-1.1:1.2/0003:046D:C52B.0023/input/input14
[ 5356.089199] logitech-djdevice 0003:046D:C52B.0024: input,hidraw1: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:101d] on usb-0000:00:14.0-1.1:1
[ 5356.091077] input: Logitech Unifying Device. Wireless PID:2007 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1.1/3-1.1:1.2/0003:046D:C52B.0023/input/input15
[ 5356.091204] logitech-djdevice 0003:046D:C52B.0025: input,hidraw2: USB HID v1.11 Keyboard [Logitech Unifying Device. Wireless PID:2007] on usb-0000:00:14.0-1.1:2


i'd be grateful for any help, cheers!

(In reply to comment #12)
> [ 5106.918534] logitech-djreceiver 0003:046D:C52B.0020:
> logi_dj_probe:logi_dj_recv_query_paired_devices error:-32
> [ 5106.918747] logitech-djreceiver: probe of 0003:046D:C52B.0020 failed with
> error -32

It appears that the kernel driver is having trouble talking to the device. It's either a kernel bug or a hardware problem. Not related to this bug.

thanks for the quick reply - i'll open a new bugreport then.

filed it under Bug 840391, thanks again!