Operating System: CachyOS Linux (Arch Linux)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 6.3.2-1-cachyos-lto (64-bit)
Graphics Platform: Wayland
KDE shows 3 devices in the mouse section. Actually there is only one connected.
Generic usb audio consumer control ¿?
Logitech MX Keys (this is the keyboard)
Logitech MX Master 3 (this is the only real mouse connected)
Which mouse is KDE really using?
Where does this “generic usb audio consumer control” device come from?
I have a problem with the mouse scroll being too fast but with this mouse mix in the configuration…
Please run sudo libinput list-devices and show the output here
More than likely your keyboard (and whatever the audio device is) is reporting itself as a mouse, which is common for a lot of modern keyboards because they like to stick scrollwheels in them now, and they usually reuse the same board in their whole product line. It should be harmless though, as long as you select the right mouse to configure in the KCM.
1 Like
Device: Power Button
Kernel: /dev/input/event1
Group: 1
Seat: seat0, default
Capabilities: keyboard
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock: n/a
Left-handed: n/a
Nat.scrolling: n/a
Middle emulation: n/a
Calibration: n/a
Scroll methods: none
Click methods: none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles: n/a
Rotation: 0.0
Device: Power Button
Kernel: /dev/input/event0
Group: 2
Seat: seat0, default
Capabilities: keyboard
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock: n/a
Left-handed: n/a
Nat.scrolling: n/a
Middle emulation: n/a
Calibration: n/a
Scroll methods: none
Click methods: none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles: n/a
Rotation: 0.0
Device: Generic USB Audio Consumer Control
Kernel: /dev/input/event9
Group: 3
Seat: seat0, default
Capabilities: keyboard pointer
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock: n/a
Left-handed: n/a
Nat.scrolling: disabled
Middle emulation: n/a
Calibration: n/a
Scroll methods: none
Click methods: none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles: n/a
Rotation: 0.0
Device: Generic USB Audio
Kernel: /dev/input/event10
Group: 3
Seat: seat0, default
Capabilities: keyboard
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock: n/a
Left-handed: n/a
Nat.scrolling: n/a
Middle emulation: n/a
Calibration: n/a
Scroll methods: none
Click methods: none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles: n/a
Rotation: 0.0
Device: Logitech MX Keys
Kernel: /dev/input/event8
Group: 4
Seat: seat0, default
Capabilities: keyboard pointer
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock: n/a
Left-handed: n/a
Nat.scrolling: disabled
Middle emulation: disabled
Calibration: n/a
Scroll methods: none
Click methods: none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles: flat *adaptive custom
Rotation: 0.0
Device: Logitech MX Master 3
Kernel: /dev/input/event11
Group: 5
Seat: seat0, default
Capabilities: keyboard pointer
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock: n/a
Left-handed: disabled
Nat.scrolling: disabled
Middle emulation: disabled
Calibration: n/a
Scroll methods: button
Click methods: none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles: flat *adaptive custom
Rotation: 0.0
Device: Eee PC WMI hotkeys
Kernel: /dev/input/event3
Group: 6
Seat: seat0, default
Capabilities: keyboard
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock: n/a
Left-handed: n/a
Nat.scrolling: n/a
Middle emulation: n/a
Calibration: n/a
Scroll methods: none
Click methods: none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles: n/a
Rotation: 0.0
The two “wrong” devices both report “pointer” (as well as keyboard) capability, that’s why they are considered mice.
As redstrate suggests this probably makes some kind of sense on a technical level.
Not sure what to do about it. Maybe libinput shouldn’t advertise pointer capability. Maybe Plasma should ignore pointing devices that also have keyboard capability. But what if I have a genuine mouse that also has keyboard capabilities?
1 Like
Yes, it’s a valid concern because some gaming mice with a bunch of buttons unfortunately advertise themselves as keyboards.
Using libinput debug-events I have seen that KDE uses the proper mouse: Logitech MX Master 3.
As for the excessive mouse scroll speed, it is a kernel bug: 216885 – HID++ Logitech G903 generates full scroll wheel events with every hi-res tick when attached via USB
1 Like
btw, there not a single mouse “KDE uses”. All connected devices can send input events that will be processed