Bug 24461

Summary: xf86-input-keyboard-1.4.0 mouse key acceleration not working
Product: xorg Reporter: Harald van Dijk <truedfx>
Component: Input/KeyboardAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED INVALID QA Contact: Xorg Project Team <xorg-team>
Severity: major    
Priority: high CC: nbowler, peter.hutterer
Version: 7.4 (2008.09)Keywords: regression
Hardware: x86 (IA32)   
OS: All   
Whiteboard: 2011BRB_Reviewed
i915 platform: i915 features:

Description Harald van Dijk 2009-10-11 12:11:15 UTC
After upgrading xf86-input-keyboard from 1.3.2 to 1.4.0, mouse key acceleration seems to no longer be working. I press Alt-Shift-NumLock, then hold down PgDn, and now the cursor keeps moving quite slowly, taking far longer it did with 1.3.2. It looks like that slow speed is the initial speed of 1.3.2, and the acceleration stopped working somehow, but I'm not entirely sure about that nor am I sure how to find out.
Comment 1 Harald van Dijk 2009-10-29 11:59:13 UTC
Well, I guess that's a way to resolve this, break mouse keys badly enough that missing acceleration isn't noticeable :-)

With xorg-server-1.7.1, the cursor isn't updated on the screen when I move it. If I do something which hides, then shows the cursor (for example: type anything in an xterm window, attempt to move it over a hyperlink in a browser window, ...) it gets displayed at the correct location. Mouse keys are unusable because of this. Should I report this as a new bug, or is one enough?
Comment 2 Peter Hutterer 2009-11-01 21:10:26 UTC
Separate bug please, if necessary we can merge them together again but I doubt they're caused by the same issue.
Comment 3 Peter Hutterer 2009-11-01 21:18:42 UTC
confirmed as keyboard issue, mouse accel works ok with evdev.
tested with xserver and keyboard 1.4.0

couldn't reproduce the other issue though.
Comment 4 Harald van Dijk 2009-11-02 11:30:30 UTC
Sure, I've reported the other issue as #24856.
Comment 5 Jeremy Huddleston Sequoia 2011-10-11 11:40:58 UTC
Bumping priority since this is a regression.

Peter, you reproduced this 2 years ago.  Did it get fixed and just not closed?  
If it's still an issue, what is blocking its progress now that you can 
reproduce it?
Comment 6 Peter Hutterer 2011-10-12 22:53:24 UTC
(In reply to comment #5)
> If it's still an issue, what is blocking its progress now that you can 
> reproduce it?

None of my users use the keyboard driver and have no time fixing it (if the bug is still present).
Comment 7 Adam Jackson 2018-06-12 19:08:50 UTC
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.