Physically plugging in a single USB keyboard triggers a large number of confirmation dialog boxes for attaching devices to dom0

[h01ger]

Qubes OS release

Qubes OS 4.2

Brief summary

I¨ve got a new 4.2 install and when I attach a usbc docking station to which an usb keyboard is attached, it aske me eight times to confirm whether I want to attach that keyboard to dom0. To make matters worse, I have to move the mouse pointer away from that window and back again so that the ok button becomes pressable.

Steps to reproduce

Expected behavior

No response

Actual behavior

No response

Additional information

No response

[marmarek]

I'm pretty sure those are actually separate devices, and you don't need (or want) to allow all of them, you need just one or two. But due to https://github.com/QubesOS/qubes-issues/issues/2783 you don't have any clue which one...

[h01ger]

hm, but I only have one keyboard connected and I am pretty sure it said keyboard each time.

-- cheers, Holger

⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄

The ongoing cognitive decline of common people are too gradual to be noticed by the people whose cognitions have been gradually declined.

[unman]

What happens if you attach the docking station without the keyboard attached? Or attach the keyboard without using the docking station?

[h01ger]

On Sat, Jun 14, 2025 at 04:44:27AM -0700, unman wrote:

What happens if you attach the docking station without the keyboard attached?

excellent question!

I get 5 times the keyboard question and 1 time the mouse question.

Or attach the keyboard without using the docking station?

I got the keyboard question three times.

Interestingly, when attached to the dock and then attaching the keyboard to the dock, I only get 2 more keyboard questions. (but not 3).

Then adding another keyboard directly, I get the keyboard question 3 times again.

-- cheers, Holger

⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄

"If you get tired, learn to rest, not to quit." -- Banksy

[unman]

On Sat, Jun 14, 2025 at 05:09:55AM -0700, Holger Levsen wrote: [quote] I get 5 times the keyboard question and 1 time the mouse question. [/quote] Hmmm

[marmarek]

Some keyboards have multimedia keys as separate devices. Observe dmesg in sys-usb at the time you plug it in, you should see device description there. Alternatively, evtest tool (in sys-usb) will show you a list of connected HID devices.

[h01ger]

Some keyboards have multimedia keys as separate devices. Observe dmesg in sys-usb at the time you plug it in, you should see device description there.

there´s really not much:

[user@sys-usb ~]$ sudo dmesg |grep -i usb|grep -i key
[   63.890158] usb 8-1.3.4: Product: USB Keyboard
[   63.972333] input: Logitech USB Keyboard as /devices/pci0000:00/0000:00:09.0/usb8/8-1/8-1.3/8-1.3.4/8-1.3.4:1.0/$ANON/input/input7
[   64.046905] hid-generic 0003:046D:C34B.0003: input,hidraw2: USB HID v1.10 Keyboard [Logitech USB Keyboard] on usb-$ANON.0-1.3.4/input0
[   64.054361] input: Logitech USB Keyboard as /devices/pci0000:00/0000:00:09.0/usb8/8-1/8-1.3/8-1.3.4/8-1.3.4:1.1/$ANON/input/input8
[   64.105031] hid-generic $ANNN: input,hidraw3: USB HID v1.10 Device [Logitech USB Keyboard] on usb-0000:00:09.0-1.3.4/input1
[   65.036991] hid-generic $ANNO: input,hidraw6: USB HID v1.11 Keyboard [Microsoft Microsoft® Nano Transceiver v2.0] on usb-0000:00:09.0-1.3.3.4/input0

Alternatively, evtest tool (in sys-usb) will show you a list of connected HID devices.

It´s currently not installed in sys-usb, so I´ll need to install it in the template and restart sys-usb - which I´d rather not do right now...

[marmarek]

So, you've got 3 logical devices there (at least, there may be others not matching your grep pattern):

• USB HID v1.10 Keyboard [Logitech USB Keyboard]
• USB HID v1.10 Device [Logitech USB Keyboard]
• USB HID v1.11 Keyboard [Microsoft Microsoft® Nano Transceiver v2.0]

My guess the first one handles most keys, the second may handle some special (multimedia?) keys, and the last one is something else (some wireless interface? or maybe some configuration endpoint?)

It´s currently not installed in sys-usb, so I´ll need to install it in the template and restart sys-usb - which I´d rather not do right now...

There is also some info in sysfs: grep NAME= /sys/class/input/event*/device/uevent, but it won't be as nicely decoded as evtest (especially, evtest can nicely list what keys are advertised by which device, getting this manually requires decoding a long bitmask in the KEY= entry...)

[h01ger]

funny thing that keyboard is not a multimedia keyboard at all. it´s a boring logitech keyboard with usb cable...

I'll check the evtest output "soon" (tm)...

thanks so far!