Bug 182677

Summary:	mouse pointer acceleration settings not honoured after replugging in usb port
Product:	[Applications] systemsettings	Reporter:	Unknown <null>
Component:	kcm_mouse	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED FIXED
Severity:	minor	CC:	arysin, felipelorenzzon, mieszcz, mikebwilliams, nate, sgh
Priority:	NOR
Version:	5.24.5
Target Milestone:	---
Platform:	Manjaro
OS:	Linux
Latest Commit:		Version Fixed In:	4.5
Sentry Crash Report:

Description Unknown 2009-02-01 10:36:48 UTC

Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

Hi,
I have a HP/Compaq nc6400 laptop and a Logitech standard laser mouse.

The default acceleration was very fast and so I have set the Pointer acceleration to 0.6x in the system settings->mouse->advanced page.

When I unplug and replug the usb end of the mouse, the mouse moves very fast again and it doesn't take the custom acceleration value set. But when I change the acceleration settings (in fact to the same value) and click Apply button, it starts working normally.

Could you please help in solving this?

Thanks a lot...

Comment 1 Mike Williams 2009-07-12 17:51:23 UTC

I can confirm this bug. 

I recently installed a KVM switch that allows you to connect one keyboard/mouse/monitor to two computers, and switch between them. This has the effect of unplugging the mouse and plugging it back in every time I switch. I set my acceleration to 0.7x on this mouse, and while the option still says 0.7x, the acceleration is reset every time.

Comment 2 Mike Williams 2009-07-12 17:53:29 UTC

*** Bug 167091 has been marked as a duplicate of this bug. ***

Comment 3 Søren Holm 2010-02-17 21:21:38 UTC

It still present in KDE 4.4.

Comment 4 Christoph Feck 2010-03-11 22:30:30 UTC

Related: bug 230287

Comment 5 Andriy Rysin 2010-05-28 04:49:23 UTC

I've got a fix for a trunk in my playpen (reusing hotplug engine of keyboard daemon) but I'd like to test it a bit more. Hopefully will push tomorrow.

Comment 6 Andriy Rysin 2010-05-29 15:31:04 UTC

SVN commit 1132043 by rysin:

Refactor xinput event handling so we can handle new mouse event as well
BUG: 182677

 M  +1 -1      CMakeLists.txt  
 M  +9 -8      README  
 M  +1 -2      TODO  
 M  +0 -11     kcm_keyboard.cpp  
 M  +1 -11     keyboard_applet.cpp  
 M  +14 -3     keyboard_daemon.cpp  
 M  +3 -2      keyboard_daemon.h  
 M  +10 -6     layout_widget.cpp  
 M  +0 -10     layout_widget_plugin.cpp  
 M  +38 -24    x11_helper.cpp  
 M  +7 -13     x11_helper.h  
 D             x11_helper_xinput.cpp  
 A             xinput_helper.cpp   x11_helper_xinput.cpp#1130912 [License: GPL (v2+)]
 AM            xinput_helper.h   [License: GPL (v2+)]


WebSVN link: http://websvn.kde.org/?view=rev&revision=1132043

Comment 7 Andriy Rysin 2010-05-29 16:28:29 UTC

I've pushed the fix in trunk, and if somebody can confirm it works that'd be great

Comment 8 felipelorenzzon 2022-05-28 21:06:31 UTC

In Manjaro with Plasma 5.24.5, this bug is still present. In fact, I have noticed it a few weeks ago. Unplugging my Redragon M710 10000dpi mouse and plugging it again causes the sensitivity to reset. I haven't tested other mice. If I remember correctly, it is also present in Fedora 35 (I can retest this if you want).

The way I manually solve this is by going to mouse settings, changing the sensitivity to any value, saving, then changing it to my desired value and saving again.

By the way, it would be nice if the sensitivity scale could be set to a lower value. I use the lowest sensibility available and some people think it is still too high.

Comment 9 Nate Graham 2022-08-24 22:01:54 UTC

The bug that was fixed here is different from yours as the entire backend code and driver stack has completely changed since 2010. :) Your issue is most likely Bug 457928.