https://bugs.kde.org/show_bug.cgi?id=465957
Peter van der Woude <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #29 from Peter van der Woude <[email protected]> --- I had this issue, it's slightly cleaner example... My Logitech G Pro Wireless Gaming Mouse (046d:c088), USB wired (no dongle), shows twice in System Settings → Mouse & Touchpad device dropdown. Plasma 6.7.4, libinput 1.31.3, kernel 7.2.3-1-cachyos (Arch-based). The mouse registers two HID interfaces via hid-logitech-hidpp: ``` N: Name="Logitech G Pro Wireless Gaming Mouse" P: Phys=usb-0000:00:14.0-10.4/input0 H: Handlers=event5 mouse0 U: Uniq=EF84973A81AAB954 B: EV=17 B: REL=1943 N: Name="Logitech G Pro Wireless Gaming Mouse" P: Phys=usb-0000:00:14.0-10.4/input1 H: Handlers=sysrq kbd leds event7 U: Uniq=EF84973A81AAB954 B: EV=12001f B: REL=1040 ``` udev and libinput classify them correctly: ``` event5: ID_INPUT_MOUSE=1 LIBINPUT_DEVICE_GROUP=3/46d/c088:usb-0000:00:14.0-10 event7: ID_INPUT_KEYBOARD=1 LIBINPUT_DEVICE_GROUP=3/46d/c088:usb-0000:00:14.0-10 ``` The second interface (input1) has no REL_X/REL_Y REL=0x1040 is only REL_HWHEEL_HI_RES and REL_WHEEL_HI_RES. It's tagged ID_INPUT_KEYBOARD, not ID_INPUT_MOUSE. So the KCM could safely filter this: **if a device lacks REL_X/REL_Y and is not tagged ID_INPUT_MOUSE, then just don't show it in the mouse dropdown**. Gaming mice that report as keyboard+pointer still have pointer axes, so they'd be OK. (BTW even worse, to the idea this does look bad.... my mouse's battery was detected as a system battery! and so my desktop was put into Power Save mode with no GUI way to take it out, and that power mode put my wifi into power save mode which meant constant dropped connections and terrible gaming performance... so only an enthusiast would persist with what's happened to me) -- You are receiving this mail because: You are watching all bug changes.
