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 352154 - Bon Echo's Add Bookmark dialog hangs Orca; Bon Echo crashes
Bon Echo's Add Bookmark dialog hangs Orca; Bon Echo crashes
Status: RESOLVED WONTFIX
Product: orca
Classification: Applications
Component: general
0.2.x
Other All
: Normal critical
: ---
Assigned To: Orca Maintainers
Orca Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-20 17:31 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2006-08-22 15:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Joanmarie Diggs (IRC: joanie) 2006-08-20 17:31:38 UTC
Please describe the problem:
If Orca is running, getting into Bon Echo's Add Bookmark dialog hangs Orca and causes Bon Echo to crash.  

Steps to reproduce:
1. Launch Orca
2. Launch Firefox Bon Echo Beta 1
3. Press Control D


Actual results:
1. The system hangs for a bit
2. Bon Echo eventually crashes
3. Orca hangs and its processes must be killed to resume normal operation

Expected results:
The above wouldn't happen. :)

Does this happen every time?
Yes.

Other information:
I am using Ubuntu Edgy, Bon Echo Beta 1, and the latest (as of this moment) Orca from CVS HEAD.

If Orca isn't running, I can add bookmarks as expected.
Comment 1 Willie Walker 2006-08-21 14:37:42 UTC
I'm able to make Bon Echo crash this way, but Orca doesn't seem to hang.
Comment 2 Joanmarie Diggs (IRC: joanie) 2006-08-21 15:37:04 UTC
When I do it, I get a bunch of COMM_FAILURES.  Orca tries 5 times and then gives up.  But as best as I can tell, it tries 5 times each for lots and lots of events.  The end result is that the system grinds to a (silent) halt until I terminate the Orca-related processes.

On one of my machines, I also tend to get an AT-SPI crash.  This does not seem to be the case (most of the time) on the other machine.

Is there something I can do to help you track this down?
Comment 3 Willie Walker 2006-08-21 16:24:37 UTC
Earlier this year, we worked pretty hard to try to identify and resolve issues with accessibility to Firefox 2.  After much discussion and work, the larger community (including the Firefox folks) decided that investing in Firefox 2 accessibility was not an efficient use of resources.  So...we decided to focus on providing compelling access to Firefox 3.  Over the summer, the Sun and IBM Firefox teams have been plugging away at this and they are almost ready for others to start taking it for a test ride.

As such, our forward looking plans will be to start looking at Firefox 3 with Orca  as soon as GNOME 2.16 is released.  If you want to be on the cutting edge, you might try to beat us to the test ride and start looking at Firefox 3.  :-)
Comment 4 Joanmarie Diggs (IRC: joanie) 2006-08-21 16:33:15 UTC
Understood.  Will do. :-)
Comment 5 Willie Walker 2006-08-22 15:42:19 UTC
I'm going to close this out with "won't fix," but that means politely for Firefox 2.  We'll be much more aggressive for Firefox 3 and Orca V1.0+.  Thanks!