maemo.org Bugzilla – Bug 5972
Race condition with hardware shift key
Last modified: 2010-01-14 12:28:54 UTC
You need to
before you can comment on or make changes to this bug.
STEPS TO REPRODUCE THE PROBLEM:
1. Open an application that accepts text input.
2. Press shift.
3. Quickly press two or more characters.
Only one shifted character appears from one press of the shift key.
I've been able to get up to 5 shifted characters to appear from one press of
the shift key.
Sometimes, depending on CPU load and character entry speed.
This makes rapid text entry rather obnoxious since you end up with a lot of
extra shifted characters.
User-Agent: Mozilla/5.0 (X11; U; Linux armv7l; en-US; rv:1.9.2a1pre)
Gecko/20090928 Firefox/3.5 Maemo Browser 220.127.116.11 RX-51 N900
It seems (xev is no help here) to happen when a key is pressed before any of
the previous ones is released. Example (mostly ignoring effects of autorepeat
for simplicity, some finger gymnastics required):
1. Press and release Shift.
2. Press and hold Z (Z is entered).
3. Press and hold X (X is entered).
4. Press and hold V (V is entered).
5. Release Z or X (autorepeat produces "v" characters).
A second key press should trigger the shift state reset, instead of waiting for
a key release.
(In reply to comment #1)
> It seems (xev is no help here) to happen when a key is pressed before any of
Here's a xev that works under Fremantle: http://qwerty12.qole.org/xev
(Diff here: http://qwerty12.qole.org/xev.diff)
(In reply to comment #2)
> Here's a xev that works under Fremantle: http://qwerty12.qole.org/xev
> (Diff here: http://qwerty12.qole.org/xev.diff)
Thanks! Of course now I realize that it doesn't help anyway as it grabs the
input before him sees it...
But, why isn't this already in bugzilla? Do file a bug with the patch, you
know you want to ;-)
(In reply to comment #3)
> But, why isn't this already in bugzilla? Do file a bug with the patch, you
> know you want to ;-)
This has been fixed in package
which is part of the internal build version
(Note that 2009 is the year and the number after is the week.)
Any public update released with or after this build version will include the
Please verify that the new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.
*** Bug 7548 has been marked as a duplicate of this bug. ***
The problem reported here should be fixed in the update released today for
public: The Maemo5 update version 2.2009.51-1 (also called "PR1.1" sometimes).
Please leave a comment if the problem is not fixed for you in this update