Bug 511068 - If the PC has a single account; make the mouse/touchpad speed the same
Summary: If the PC has a single account; make the mouse/touchpad speed the same
Status: RESOLVED INTENTIONAL
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_sddm (other bugs)
Version First Reported In: 6.5.0
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2025-10-25 05:19 UTC by Fernando Marcelino Muniz
Modified: 2025-10-29 20:01 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fernando Marcelino Muniz 2025-10-25 05:19:08 UTC
STEPS TO REPRODUCE
1. Have a single account on your PC.
2. Have a high mouse/touchpad speed.
3. Restart and move your mouse/touchpad.

OBSERVED RESULT
It uses the default/non-opionated speed, which is very slow.

EXPECTED RESULT
Since I only have one account, the login manager should just use the same mouse/touchpad speed that I have on my user account.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.5.0
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.5-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-11300H @ 3.10GHz
Memory: 9 GB of RAM (8.1 GB usable)
Graphics Processor 1: Intel® Iris® Xe Graphics
Graphics Processor 2: NVIDIA GeForce GTX 1650
Manufacturer: LENOVO
Product Name: 82MG
System Version: IdeaPad Gaming 3 15IHU6
Comment 1 Nate Graham 2025-10-29 18:47:47 UTC
This sounds easy, but it's actually almost impossible to implement as described. That's why there's a "manually sync settings" feature.

Once we have plasma-login-manager, it *may* be more technologically feasible to do things like this, but it's premature for me to be able to predict one way or another.
Comment 2 Oliver Beard 2025-10-29 20:01:07 UTC
I concur. From a plasma-login-manager perspective, doing this outside of sync would still be infeasible. It would be best as a global setting that would affect all users on the system, and that could be challenging for reasons that I am unaware of.