GNOME Bugzilla – Bug 678936
enabling then disabling orca caused crash.
Last modified: 2012-08-14 20:30:12 UTC
I launched the orca application, and enabled speech through the command-line setup. Then it told me that it would be enabled when I logged in and out, and asked me if I would like to log out. However, the terminal window had already closed. Then I opened orca without logging out, and the speech was working. I then disabled 'enable speech' in the preferences box and pressed 'OK'. Speech stopped. Then I quit orca, and the window floated for a bit, then gnome shell became completely unresponsive. I switched to a tty and killed (-9) both processes that grepped of orca. That fixed gnome shell. Then I reopened it, and quit without problems. Later, I reopened it, and either right away or after I opened the prefereces window, orca was talking again. I hit 'cancel', then quit, and the same gnome-shell unresponsiveness occurred. I fixed it the same way.
Orca 3.2 is no longer being maintained. Can you reproduce this in Orca 3.4 or (better still) Orca 3.5.x? There have been many changes to both gnome-shell and Orca since GNOME 3.2.
Created attachment 217402 [details] orca configuration files
I still had this issue in 3.2.1 after I restarted the computer. The OS was Trisquel 5.5, based on Ubuntu 11.10. I also tried it on debian wheezy, with gnome 3.4.x. I had a very similar problem with orca, but it wasn't as bad. When I told orca to quit, it hung after several seconds. Then it would unhang a few to several seconds later, and the quit dialog would pop back up with the 'quit' button selected. I waited and it still did not quit. so I clicked the 'x' or 'close' button from the window manager and a few seconds later got a window that asked me if i wanted to force quit the program. i said no, and then I got it to hang again, perhaps by clicking the quit button on orca's main window again. i clicked 'x' on the quit window and agreed to force quit the program. After that, gnome-shell crashed after I opened gedit, and then logging back in created an unresponsive gnome-shell. I rebooted into Trisquel. I've attached the config files that come from Trisquel and were shared with Debian Wheezy.
I just tried launching orca in gnome 3.2.1 fallback mode (Trisquel 5.5). I quit the program, and the said 'quit' when the quit box came up, but it did not quit. However, the fallback mode did not hang. When I moved a window over the orca windows and away again, their contents became blank.
The current Orca is 3.5.x (and 3.7.x if you are in a Python 3 environment). I am pretty sure this problem was fixed already. If you can reliably reproduce it using Orca 3.5.x or 3.7.x please reopen this bug.