Bug 438266 - Make it clearer which mouse is being configured when multiple mouse devices are available
Summary: Make it clearer which mouse is being configured when multiple mouse devices a...
Status: CONFIRMED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_mouse (show other bugs)
Version: 5.22.0
Platform: Neon Linux
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: usability
: 447089 (view as bug list)
Depends on:
Blocks:
 
Reported: 2021-06-08 15:46 UTC by Jeffrey Bouter
Modified: 2024-03-25 03:39 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeffrey Bouter 2021-06-08 15:46:16 UTC
SUMMARY

When using "Invert Scroll Direction" for mice on Wayland, this actually does nothing. Natural Scrolling for touchpads, however, works fine. Libinput also reports "Nat. Scrolling" to be disabled.

STEPS TO REPRODUCE
1. Use a Wayland session
2. Select "Invert scroll direction" under system settings > Hardware > Input Devices > Mouse
3. Try scrolling in any window

OBSERVED RESULT

Scrolling direction does not change

EXPECTED RESULT

Scrolling direction to be inverted

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.22.0
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION

libinput information on my MX Vertical (which is actually reported three times).

Device:           Logitech MX Vertical Advanced Ergonomic Mouse
Kernel:           /dev/input/event9
Group:            10
Seat:             seat0, default
Capabilities:     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
Accel profiles:   flat *adaptive
Rotation:         n/a


Device:           Logitech MX Vertical
Kernel:           /dev/input/event13
Group:            8
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
Accel profiles:   flat *adaptive
Rotation:         n/a

Device:           Logitech MX Vertical Advanced Ergonomic Mouse Keyboard
Kernel:           /dev/input/event10
Group:            10
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
Accel profiles:   n/a
Rotation:         n/a


Libinput information on my Steelseries Rival 100:

Device:           SteelSeries SteelSeries Rival 100 Gaming Mouse
Kernel:           /dev/input/event23
Group:            11
Seat:             seat0, default
Capabilities:     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
Accel profiles:   flat *adaptive
Rotation:         n/a
Comment 1 Nate Graham 2021-06-14 15:16:42 UTC
In fact none of the mouse settings seem to be working in the Plasma Wayland session.
Comment 2 Zamundaaa 2021-06-17 13:19:28 UTC
Are you choosing the correct mouse in the KCM before changing the settings? Works just fine here but the wrong mouse device was set by default.
Comment 3 Nate Graham 2021-06-17 13:53:16 UTC
Hmm, that's a possibility. Let me check the next time I'm doing a Wayland QA day.
Comment 4 Jeffrey Bouter 2021-06-18 06:51:43 UTC
Zamundaaa is absolutely right. The mouse settings can be adjusted by selecting the proper device. However, considering both Nate and I overlooked this option, perhaps this needs to be made a tad clearer in the settings.
Comment 5 Nate Graham 2021-07-12 02:16:40 UTC
Yes, it does indeed depend on having the right mouse selected. On my ThinkPad, the trackpoint appears as a second mouse.
Comment 6 Nate Graham 2021-08-03 21:31:02 UTC
Part of the problem for me at least is that my trackpoint appears as a mouse. That's pretty unexpected.
Comment 7 Nate Graham 2024-03-25 01:50:07 UTC
*** Bug 447089 has been marked as a duplicate of this bug. ***