Bug 327674

Summary:	mouse acceleration profile bug
Product:	[Applications] systemsettings	Reporter:	Scott <westlake.bugs>
Component:	kcm_mouse	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	simon.thum, unassigned-bugs
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian stable
OS:	Linux
Latest Commit:		Version Fixed In:
Bug Depends on:	235630
Bug Blocks:

Description Scott 2013-11-16 04:14:17 UTC

KDE desktop starts with 
"Device Accel Profile (253):	0"
for my mouse despite Accel profile set to 2 in xorg.conf

I tried discussing for a solution on kde@mail.kde.org (including looking at KDE settings of 'Common appearance and Behaviour/Customshortcuts/global_keybshortcuts'  'Kwin' disabling any shortcut bindings to 'Move mouse to center' and 'Move mouse to focus')

xinput --list-props <device> is the tool I use to list and change the accel profile from 0 to 2
(xinput --set-prop <device> 'Device Accel Profile' 2)

When set to 2, immediately the following symptom occurs.

Symptom: Every 5 seconds the mouse cursor jumps to an edge of a screen (if I move the mouse 1 pixel up, it jumps to the edge of the top screen directly up.  If diagonal, it goes to corner, etc..)

Immediately setting the accel profile back to 0, this symptom doesn't recurr..

Shouldn't KDE inherit xorg's mouse accel profile? KDE changes it from somewhere..

fwiw, the acceleration profile for '2' means polynomial.. there's 7 of them, 

the one I have selected is one of the modern ones (it works with the GNOME login, so I don't see why it shouldn't work with KDE.. my mouse works best with this acceleration profile)

http://xorg.freedesktop.org/wiki/Development/Documentation/PointerAcceleration (AccelerationProfile [integer] subsection)

Thanks..

Comment 1 Scott 2013-11-16 04:22:59 UTC

I believe there's a typo on that page, it should be saying
"0" (the xorg.freedesktop.org) instead of -1 none

.. i'll be emailing the administrator for that webpage (as I've tried in the past to use -1 as an accel profile in other Desktops and wasn't possible, but '0' certainly is)

Comment 2 Simon Thum 2015-01-05 20:01:37 UTC

A bit late now, but to clarify, -1 is "none" i.e. no dynamic acceleration or deceleration.

The man page should be used as the authorative source. The wiki page is slightly involved, it's mainly for devs.

I suspect the profile is not changed at all, or it is being overridden. KDE never used to chnage the profile, it only cares about the "feedback" settings you can change using xset. That's not fortunate, but anyway.

About the bug, this is probably "to be expected". The aforementioned feedback is kept while changing profiles, and profiles build on the feedback for parametertization. To avoid that, always change profiles together with feedback that is safe for the profile. E.g.

xinput set-ptr-feedback <device name> <threshold> <num> <denom>
xinput set-prop <device> "Device Accel Profile" <profile_number>

Comment 3 Simon Thum 2015-01-05 20:04:09 UTC

That said, the very least KDE should do is not interfere with feedback the way it does ATM.

Comment 4 Simon Thum 2015-01-05 20:07:12 UTC

Which reminds me that I filed bug #235630 for that. I guess this bug counts as confirmation.

Comment 5 Justin Zobel 2021-03-09 07:29:44 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.

Comment 6 Nate Graham 2024-03-25 01:40:31 UTC

Hello! This Bugzilla ticket concerns support for the non-Libinput version of the Mouse page, which is no longer supported in Plasma 6. As such, the ticket will be closed as fixing or implementing what's requested here is now out of scope.

Thanks for your understanding!