SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Plug in single mouse 2. Start Wayland Session 3. Check device combobox under System Settings-->Input Devices-->Mouse OBSERVED RESULT Shows three options, one of which is my mouse. If options other than the mouse are selected, the sliders/options have no effect. By default, an unknown USB device was selected. EXPECTED RESULT Combo box should only contain one option unless more than one mouse is plugged in. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.17.1.arch1-1 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I have seen something similar on XFCE in their libinput options screen in the past so I don't know if its actually a KDE-specific issue. I initially made a bug report assuming the sliders simply weren't working (https://bugs.kde.org/show_bug.cgi?id=451296) only to be told (thanks Nate!) that there's a combobox in Wayland when there wasn't in X11. My combo box contains three options: "SONiX USB Device" (this was the default), "Wing Tech Xtrfy M42" (the one that works), and "Wing Tech Xtrfy M42 Keyboard". The mouses' actual name is the Xtrfy M42.
I see this too: the combo box lists the keyboard as well as the mouse. Using lshw, the two devices are reported thus: *-usb:0 description: Keyboard product: USB Keyboard vendor: SEM physical id: 4 bus info: usb@4:4 version: 1.10 capabilities: usb-1.10 configuration: driver=usbhid maxpower=98mA speed=2Mbit/s *-usb:1 description: Mouse product: HP USB Optical Mouse vendor: PixArt physical id: 5 bus info: usb@4:5 version: 1.00 capabilities: usb-2.00 configuration: driver=usbhid maxpower=100mA speed=2Mbit/s
Can confirm. It almost seems like each physical pointing devices gets two logical ones listed in the combobox.
touchscreen is also detected as mouse, see bug 428520
*** This bug has been marked as a duplicate of bug 437245 ***