Orca causes OpenOffice / LibreOffice Java to crash

[Michael Jonker]

Binary package hint: gnome-orca

I am experiencing the following in both Open Office and Libre Office writer:

Orca screen reader reads a portion of the complete text (when reading the whole document) and then Open/Libre office crashes with no warning or dialogue.
As soon as trying to handle an object (such as an image) writer crashes immediately with no warning or dialogue.

The attached logs show that something is going wrong in the Java environment. I have tried both OpenJDK and Sun-Java6, both with the same results and similar logs. I have attached both logs.

I have logged this as a bug with OpenJDK (Bug #752340), but feel that the problem may lie in Orca due to both Open and Sun Java reacting the same way.

Open/Libre office behaves normally when Orca is not running.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gnome-orca 2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic x86_64
Architecture: amd64
Date: Wed Apr 6 11:29:55 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
PackageArchitecture: all
ProcEnviron:
 LANG=en_IE.utf8
 SHELL=/bin/bash
SourcePackage: gnome-orca

[Luke Yelavich (themuso)]

Have you installed libaccess-bridge-java? Its part of the java access bridge. Please install this package, and try again, and report back.

Thanks

 affects ubuntu/gnome-orca
 status incomplete

[Michael Jonker (citizen-jonker)]

Yes, libaccess-bridge-java is installed (it was installed all the time) so this is not the problem.

I did a fresh re-install of Ubuntu 10.10 and the problem still persists.

I have attached the document in question for testing. (I have briefly tested other docs with similar results)

I checked the document on a Fedora 14 install and the problem does not exist in that environment.
The only difference is that I am using Metacity for compositing in Fedora and Compiz in Ubuntu.

(In case you are wondering why I bother with compositing - I am setting up Orca as part of an adult literacy program, so it is not being used only for visual impairment)

Turning off Compiz in Ubuntu (ie. no compositing at all) makes a small difference - I can select an image once or twice before Writer crashes. With Compiz on it will crash immediately when an image is selected.

In case it matters - I have Gnome Panels turned off as well and Avant Window Navigator used as the panel manager.

I will test Fedora/Compiz in a while and report back.

I have reported this bug at LibreOffice as well: https://bugs.freedesktop.org/show_bug.cgi?id=36023

[Michael Jonker (citizen-jonker)]

I tested on Fedora 14 with Avant Window Navigator with Compiz and Gnome Panels disabled and everything is working and stable.

Seems that the problem is Ubuntu specific.

[Luke Yelavich (themuso)]

Ok, I'd like you to get me a debug log from Orca, so this can be tracked down further. Please follow the following steps to get this log.
1. Go into Orca's preferences, and go to keyboard shortcuts. In there, you will find an option to change Orca's debug level. It currently is unbound, so you will find it amongst the unbound keyboard commands. Assign it a shortcut, and apply the changes.
2. Quit orca, and open a terminal. Launch Orca from a terminal, like so: orca 2>&1 > orca-debug.log.
3. Open LibreOffice, and get things ready to reproduce the crash.
4. Use the newly assigned debug toggle shortcut to toggle Orca's debug level to all.
5. Reproduce the crash.

If orca still appears to be running in the terminal, open another terminal and run orca -q, as orca in its controlling terminal cannot be killed with Control + C.

Then if you could attach the log to this bug, I'd appreciate it.

Thanks.

[Michael Jonker (citizen-jonker)]

Thanks Luke,

I tried that with the following result:

With debug logging running the system freezes completely at the point of error.
Without debug running the error occurs as per original desription and the system remains stable.

I have to hard-reset to unlock the system after debug crash. The system tells me "AT SPI registry" is not responding.

After restart I check the resultant orca-debug.log file, but it is empty.

I have uploaded a short video of what is happening here:

http://www.youtube.com/watch?v=HBWRjG9T2Xg

[Alex ARNAUD (alexarnaud)]

Hello Michael Jonker,

Are you still able to reproduce this bug?

Best regards.