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 608544 - Firefox crashes with NO speech!
Firefox crashes with NO speech!
Status: RESOLVED NOTGNOME
Product: orca
Classification: Applications
Component: speech
2.29.x
Other Linux
: Normal critical
: ---
Assigned To: Orca Maintainers
Orca Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-01-30 17:16 UTC by Steve Holmes
Modified: 2010-04-05 03:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Debug log during the crash (8.87 KB, application/x-gzip)
2010-01-30 17:16 UTC, Steve Holmes
Details

Description Steve Holmes 2010-01-30 17:16:45 UTC
Created attachment 152641 [details]
Debug log during the crash

This is unfortunately not easily repeatable but serious non the less.

Occasionally and more frequently lately, Firefox will crash with some
kind of dialog and no speech from orca.  I am attaching a debug log to
this bug report to show the several backtraces which happened.

1. Launch gnome and Orca in the usual way.
2. Go to the desktop and launch Firefox.
3. While the default page is showing, start arrowing around in the
text and especially in the table area.
4. For me this morning, I finally lost speech while pressing the up
arrow key.  On other occasions, I have lost speech while using table
navigation keys.  
5. If I hit the escape at this point, Firefox goes away and Orca
returns with full speech.

While attempting to file this bug earlier, I lost speech completely
and had to restart gnome to get things going.  This seems to be
happening with greater frequency lately so I will need to file this as
a critical bug.

Orca from git 2010-01-29, Firefox 3.5.7, Arch-Linux on 32 bit
architexture with latest updates.
Comment 1 Joanmarie Diggs (IRC: joanie) 2010-01-31 21:00:19 UTC
Steve on the Orca list you indicated that you could get out of this situation by pressing Escape to make the mystery dialog go away. I'm quite curious as to what the mystery dialog is. Therefore, the next time the problem appears, would you please try the following before you press Escape:

1. Press Alt+Print screen to take a screen shot

2. Press Return (for the default button Save in the Save Screenshot dialog.

3. Press Escape to recover as you described on the list.

4. Look around for the screenshot. I believe the location defaults to being the same, so if you took a screenshot when everything was working correctly, you should be able to identify where the screenshot will wind up when you have no speech.

If you're able to do this, please attach the screenshot to this bug. Thanks!
Comment 2 Joanmarie Diggs (IRC: joanie) 2010-02-15 01:02:09 UTC
Changing to NEEDINFO because I cannot reproduce it, and I'd really like the screenshot I mentioned in my previous comment if that would be possible.
Comment 3 Steve Holmes 2010-02-15 06:41:12 UTC
Yeah so would I.  Since I filed this thing, I can't make it happen anymore.  It blew up multiple times over that weekend but since then, I installed FF 3.6.2 and then just now fell back to 3.5.7 due to all the other bugs and I haven't had the occurence with either version since.  The only difference is now when I run FF 3.5.7, I am using a binary from Mozilla where the other 3.5.7 version was from an Arch Linux package but I can't downgrade to that version anymore due to other package dependencies.  So if this can't h=happen anymore for the next week or so, I may have to close it.
Comment 4 Joanmarie Diggs (IRC: joanie) 2010-04-04 18:32:04 UTC
Steve, has this bug happened again?

Thanks!
Comment 5 Steve Holmes 2010-04-05 02:53:38 UTC
Nope.  See my comment #3.  I did get an error dialog from a completely different app with no speech but will probably have to file a new bug on that and try and gather soem background data to repro that one.
Comment 6 Joanmarie Diggs (IRC: joanie) 2010-04-05 03:26:42 UTC
Thanks Steve.

I just wanted to verify that you were no longer seeing this bug since you had indicated you'd close this bug out if you couldn't reproduce it. I'll do that now.

Sorry to hear about the new/different issue. :-( But, yeah, please collect as much data as you can and let's see about getting it resolved.