1. Orca is not speaking. What's going wrong?

See Troubleshooting Speech.

2. LibreOffice Keeps Crashing

See this LibreOffice bug which we really need them to fix. In the meantime, we've hacked around this in Orca. You can either use the latest Orca, or alternatively, place this file wherever your Orca settings are located (e.g. either in $HOME/.orca or, more likely $HOME/.local/share/orca).

3. My desktop has stopped responding. What do I do?

If you can get to a terminal, try restarting Orca by issuing another orca command in a terminal window. This will force any existing Orca process to exit and will then restart Orca. This sometimes has the effect of unhanging the desktop (which is usually due to an ill-behaved application).

Also, if you've just started a program which you believe to be the cause of the problem, press control+alt+d to show the desktop (I do this because if you use system sounds there is a little audio feedback, and if you have useful vision, you can see the difference in brightness). Next, press alt+f2 to get the run box up, and type:

killall appname

where appname is the name of the program (for example pidgin).

If orca hasn't started talking again, use the method outlined above, but enter orca into the run box instead.

Note that when you show the desktop with control+alt+d, and when you press alt+f2 from there to show the run box, if you are using system sounds (configured in your sound preferences), there is some audible feedback which will assist you. Another good audio queue is to take advantage of the new beep at the begining of a line which gnome has started doing. When you think you are in the run box, press backspace, and you should here a beep from your system speaker (if it is enabled), this is another useful trick, and will work at the begining and end of almost any input.

If none of the above methods are successful, try pressing ctrl+alt+backspace to kill the X Window System server. This should have the effect of returning you to the login screen.

4. I did something that required me to enter a password and my system hung. What's up with that?

The gnome-keyring implementation can be run in synchronous mode or asynchronous mode, and it's unfortunately up to the application developer to decide which mode to use. The synchronous mode is what causes the hang, and you need to log a bug with the application (not Orca and not gnome-keyring) to get them to fix it. :-( See also bug #540146 and comment #9 of bug #447435.

5. Why is my chat app crashing all of the time?

It's not something you said, but likely you are getting hit with an Atk bug bug #591105. The good news is that this bug has been fixed effective GNOME 2.27.90. Unfortunately, if you are using the very latest version of, say, Pidgin but an earlier version of the GNOME desktop, you may experience this crash. Ekiga and Empathy are also impacted.

What triggers the crash is examining all of the text attributes via the AT-SPI. It turns out there is a wrap mode attribute option that Gtk+ supports, but which had not been included in Atk. If an application employs that wrap mode in an object and if you access text attributes for that same object, either by displaying them in braille or by pressing Orca+F, you can crash the application in question. The solutions are therefore:

  1. Upgrade to the latest GNOME desktop, OR
  2. Build and install Atk from git master (it's actually quite simple to build Atk), OR
  3. Pester the developers of the application in question to handle this condition on their end (which we've already suggested they do), OR
  4. Don't try to access the text attributes for the application in question. You can accomplish this by setting the braille indicator for text attributes to None in the Orca Preferences dialog for an individual application. That way you can continue to access text attributes in all of the other applications which you use.

6. I am using the ubuntu 7.04 live cd, I get the desktop and Orca starts, but it only says "switching to focus tracking mode" Whats wrong with it?

For some reason the version on the cd seem to be broken. If you simply wish to try Orca out, then the ubuntu 6.10 does contain a working Orca. Alternatively, you could use a later version of the live CD (up to 8.04 at the time of this writing). Keep in mind that Orca has a good and fast development, so you will not be able to benefit from the latest accessibility changes and Orca features.

If you are installing to hard drive, then worry not, you will be able to update to the latest version as soon as the install is finished, and (preferably) you have brought your system up-to-date). If you have done so, and would like instructions on how to proceed, visit ../../DownloadInstall

7. /etc/brltty.conf is overwritten, what to do?

Please see solution, posted on the Braille page.

The information on this page and the other Orca-related pages on this site are distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


Projects/Orca/FrequentlyAskedQuestions/Troubleshooting (last edited 2013-12-28 15:37:43 by WilliamJonMcCann)