Bug 341706 - Mouse speed settings not remembered
Summary: Mouse speed settings not remembered
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_mouse (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: triaged
: 343379 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-12-09 19:58 UTC by Kai Uwe Broulik
Modified: 2018-10-27 02:23 UTC (History)
6 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Uwe Broulik 2014-12-09 19:58:36 UTC 
My mouse speed and acceleration settings are not remembered. Whenever I restart the machine or unplug the mouse (a brief unplug-plug cycle happens when pluggin in/out the AC due to USB re-initializing) the settings are forgotten and the mouse is dead slow.

I configured cursor acceleration to 10x. When I open the KCM, the setting is there and I can apply the change but as soon as the mouse is unplugged, the setting is gone.

Reproducible: Always
Comment 1 William Boren 2014-12-23 11:32:59 UTC 
Hello, I'm a google code-in student with a task of bugtriaging.

What version of KDE and which distro do you have?
Comment 2 Kai Uwe Broulik 2015-01-23 21:51:52 UTC 
The settings are now properly applied on login but not when hotplugging.
Comment 3 Christoph Feck 2015-01-27 21:28:57 UTC 
*** Bug 343379 has been marked as a duplicate of this bug. ***
Comment 4 Michael D 2015-09-24 06:54:45 UTC 
I have the same issue with my bluetooth mouse (Microsoft Sculpt Comfort). I had this same problem in KDE4 (I'm now running KF5), but after searching I had found a workaround to make the settings stick. I can't find that workaround anymore!
Comment 5 Kai Uwe Broulik 2016-01-16 19:05:44 UTC 
David R, didn't you do a patch with some udev hotplug magic?
Comment 6 David Rosca 2016-01-16 20:23:10 UTC 
Yes, I did.

What's the current status of the issue and what is your OS? Also kded output with kcm_keyboard.debug=true may show some helpful info.
Comment 7 Christoph Feck 2016-07-18 21:09:27 UTC 
If you can provide the information requested in comment #6, please add a comment.
Comment 8 Andrew Crouthamel 2018-09-26 22:14:04 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Andrew Crouthamel 2018-10-27 02:23:57 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!