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 343133 - orca reliably hangs while trying to read a man page in terminal
orca reliably hangs while trying to read a man page in terminal
Status: RESOLVED FIXED
Product: orca
Classification: Applications
Component: general
0.2.x
Other All
: Normal critical
: ---
Assigned To: Willie Walker
Orca Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-05-27 21:21 UTC by Mike Pedersen
Modified: 2006-07-25 21:25 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch to break out of flat review logic if gnome-terminal is acting up (3.34 KB, patch)
2006-05-31 14:27 UTC, Willie Walker
committed Details | Review
More work to handle bogus results from gnome-terminal (3.14 KB, patch)
2006-06-27 14:02 UTC, Willie Walker
committed Details | Review

Description Mike Pedersen 2006-05-27 21:21:15 UTC
Steps to reproduce:
1. Open terminal and type man gedit
2. While the man page is being read press CTRL.
3. 
Attempt to flat review the screen with KP7 and KP9

Stack trace:
orca hangs

Other information:
This happens with ubuntu dapper latest as of 05/27/2006 and latest orca from 
the same time.
Comment 1 Willie Walker 2006-05-30 14:46:48 UTC
I've been able to reproduce this on my machine.  It looks like this is causing a hang in gnome-terminal - if I kill gnome-terminal, Orca comes back to life.  I also wonder if this is possibly related to the minicom problem (http://bugzilla.gnome.org/show_bug.cgi?id=342840).  While that one seems to hang the desktop, killing gnome-terminal in that case also seems to free things up.
Comment 2 Javier 2006-05-31 06:29:36 UTC
The same happens when you press a "(" or a ")" and then trying to flat review the screen. Has to be with some characters set, and this happened too with Orca 0.2.3. Something has changed in the latest gnome-terminal app.
Comment 3 Willie Walker 2006-05-31 14:27:26 UTC
Created attachment 66535 [details] [review]
Patch to break out of flat review logic if gnome-terminal is acting up

The AT-SPI implementation was giving us nonsensical values for getTextAtOffset, causing a hang in subsequent calls.  This patch provides a defensive mechanism against those types of problems.
Comment 4 Willie Walker 2006-06-01 12:42:58 UTC
From Javier:

> I have recently updated my cvs copy of Orca fixing the bug #343133.
> However Orca or gnome-terminal continue hanging when flat reviewing teh
> Gnome-terminal and man pages, for example 
> Man brltty. 
> When this happends, Orca keep queueing all events on the system, and then
> when gnome-terminal is killed, Orca dies cause flat review can't do its
> purpose, at this point 
>   a traceback error on flatreview.py on line 1396 is made.

Please verify that you have (and have installed) the fix in question.  One way to check would be to look at line 1092 of /usr/lib/python2.4/site-packages/orca/flat_review.py.  If you have installed the fix, the file will have the following at line 1092:

            # (see http://bugzilla.gnome.org/show_bug.cgi?id=343133),

If you do have this, please attach the details of the traceback - they can be helpful in debugging the problem.

Thanks!
Comment 5 Willie Walker 2006-06-27 14:02:31 UTC
Created attachment 68075 [details] [review]
More work to handle bogus results from gnome-terminal

More defensive programming to detect nonsensical and handle values from gnome-terminal.  The test case for this was "man brltty" followed by a KP_7 for flat review.
Comment 6 Rich Burridge 2006-06-29 02:33:05 UTC
I just tried this and don't see any hangs. What I do see is
that when I've hit KP9 on the last object in the gnome-terminal
window (typical the --More-- (nn%) line), there is no indication
that this is the last object. Should there be?
Comment 7 Mike Pedersen 2006-06-29 03:42:57 UTC
Not really, this is just the end of the window.  At some point we might want to say bottom of window and top of window but not for 1.0 necessarily.  
Comment 8 Rich Burridge 2006-07-25 21:25:39 UTC
This appears to now be solved. Closing as FIXED.