After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 357556 - Insert key sticks after running test keystroke files
Insert key sticks after running test keystroke files
Status: RESOLVED FIXED
Product: orca
Classification: Applications
Component: general
1.0.x
Other All
: Normal normal
: ---
Assigned To: Rich Burridge
Orca Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-09-25 04:17 UTC by Mike Pedersen
Modified: 2006-09-28 16:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Attachments
Patch to fix the problem. (1.23 KB, patch)
2006-09-28 16:20 UTC, Rich Burridge
none Details | Review

Description Mike Pedersen 2006-09-25 04:17:42 UTC
When running the test keystroke files for both gnome-terminal and gedit the insert key will frequently be stuck after the test finishes.  If any of these tests are run and orca is not exited orca will behave as if the insert key is still being held down.  This could be an ubuntu edgy issue as I have been only seeing this for the last couple days.  The problem does not happen every time but it does happen quite often.  To reproduce, just run a standalone keystroke file and then press any of the arrow keys when it finishes.  You will probably hear a change in the pitch or rate.
Comment 1 Rich Burridge 2006-09-25 05:43:49 UTC
Are you getting COMM_FAILURE's at the end of these tests Mike?

I think this might be a duplicate of bug #357248. 

If so, we need to improve the handling of CORBA.COMM_FAILURE 
in processInputEvent() in input_event.py.
Comment 2 Willie Walker 2006-09-25 12:58:27 UTC
This might be a simple problem with the keystroke files themselves.  Take a look at the end of the keystroke files - it may be that they don't include any key release events (type=1) for the Insert key.  Remember also that you can run src/tools/sanity_check.py on a keystroke file to catch some gross errors such as missing release events.
Comment 3 Rich Burridge 2006-09-25 16:54:13 UTC
Yup, looks like this is indeed the problem. Certainly in
.../test/keystrokes/gedit/file-open.keys
Comment 4 Mike Pedersen 2006-09-25 17:07:24 UTC
This seems to be happening because I need to use the insert+pause to close the keystroke file.  It seems as though the keystroke file is being closed before the insert key is released.  
Comment 5 Rich Burridge 2006-09-28 16:20:56 UTC
Created attachment 73568 [details] [review]
Patch to fix the problem.

Well, it looks like there was a really good reason why the special
hot-key for starting/stopping recording of keystrokes in Orca was
Pause (rather than Insert-Pause). Because there was already code in
place to not write out the Pause keystroke.

I've reverted it back to just "Pause" and adjusted the "don't write
pause keystrokes" to recognize F21 (which is the Pause key on my Sun 
type 6 keyboard).
Comment 6 Rich Burridge 2006-09-28 16:24:31 UTC
Changes checked in CVS HEAD. Closing as FIXED.