GNOME Bugzilla – Bug 462547
OOo-dev 2.3.0 simpress application startup wizard hangs the desktop.
Last modified: 2007-08-07 18:36:26 UTC
This is going to be the tracking bug for YAOOoB which I'll file next. Thing is with the OOo-dev 2.3.0 Linux (RPM) build from 31st July 2007, on Ubuntu Gutsy (with all the latest updates), and with Orca from SVN HEAD. Steps to reproduce: 1/ Start Orca 2/ Start OOo-dev 2.3.0 simpress. The the first screen of the startup wizard will appear, with focus on the Next button. 3/ Press space. The second screen of the startup wizard will be displayed. If you have the patch from Orca bug #462256 applied, you will hear "Next button spoken too). 4/ Press space. Rather than going to the third screen, the Next button disappears and everything hangs. I did a separate test of all of this without Orca running, and simpress nicely displays the third screen.
OpenOffice issue #80267 filed. http://www.openoffice.org/issues/show_bug.cgi?id=80267
Correction. It isn't the desktop that's hung. Just simpress.
(Putting this comment where it belongs. Sorry Rich!) if in atspi.getRelationString(), I comment out relations = self.relations and make relations an empty list instead, simpress doesn't hang. If instead I wrap relations = self.relations in a try/except, it does hang. It seems that we're getting a defunct object, trying to print details, calling toString(), and making simpress really unhappy when we look at its relations.
> if in atspi.getRelationString(), I comment out relations = self.relations and > make relations an empty list instead, simpress doesn't hang. If instead I wrap > relations = self.relations in a try/except, it does hang. Right. I'm seeing the same thing. Problem is once I've Spaced the Create button on the final screen of the startup wizard, the simpress main window comes up, then after about 10-15 seconds, goes into Error Recovery mode. Unfortunately it's still unusable.
Well I've upgrade to OOo-deb 2.3.0 (build #223), plus latest Ubuntu Gutsy packages (as of today), plus latest Orca plus deleted all my GNOME "dot" files, and the problem has gone away. I've closed out the OOo issue and am closing this one as FIXED.