Apache OpenOffice (AOO) Bugzilla – Issue 94170
OOo 3.0 during initial run stops responding (requiring a force quit or a sudo kill -9) or crashes, following registration options
Last modified: 2017-04-04 16:31:36 UTC
Running release candidate 2 of OOo 3 for the first time, opted to register later. Before the OOo start center appeared, the application stopped responding. After waiting some considerable time, I opted to force quit. I'll attach the problem report. Mac OS X 10.5.5, Intel, MacBook Pro, first generation.
Created attachment 56719 [details] Problem report (submitted to Apple in the usual way following a force quit)
Subsequent launch of OOo seems to be fine. If it's relevant: during the first run routine I did _not_ enter any details in the user information fields; I was installing as an administrator of the computer (not its usual user, he is not present).
Symptoms present with release 3.0.0.
Created attachment 57143 [details] Another problem report, this time the force quit was necessary for release 3.0.0.
Created attachment 57146 [details] And again with release 3.0.0 on a different computer imac21.centrimm.freeman-centre.ac.uk
= See also = Issue 95244 > issue with UserProfile.xcu at first run/launch (both tickets relating to an issue that seems to occur only at first launch).
just tested this on a OOO300m10 (that is an early 3.0.1 build) and could not reproduce. It works ok for me.
close
And again with release 3.0.0 on yet another computer. On this occasion I did enter user details at first launch, opted to register later, suffered the crash. On second launch, no user details were present. Reminiscent of Issue 95244.
I just had a severe crash which seems to be related to a recent Apple software fix. The worst part of this is that it was on a laptop that cannot be shut down as a result, even after I force quit Ooo and some other applications. And this was not the first time I ran Ooo 3.0.0. I've only been having trouble recently, but I can't remember which Apple fix triggered it.
Subject of this ticket: "… during first run …" @ chuckdcoleman: > this was not the first time I ran Ooo 3.0.0. As the environment differs from the subject line, please create a separate ticket. Thanks. > severe crash … The worst part of this is that it was on a laptop > that cannot be shut down as a result, even after I force quit > Ooo and some other applications. I too have experienced that, and you and I are not the only people to have mentioned the symptoms in unrelated tickets ;) see for example highlights and other annotations at: http://www.diigo.com/annotated/ff23c417255b05143a8d98cf6897f0f0 http://www.diigo.com/annotated/ae21c6f831d19e87fdfb65a675cd02e9 http://www.diigo.com/annotated/d8ad77a15e5d0f28a54aa16d5bb11f17 All things considered, I suggest that each person who experiences a 'can not force quit' issue should a) check for a truly related ticket; and if none is found, b) create a ticket detailing their own situation. Regards Graham
Since the 5th November crash on first launch, I have had no more crashes on first launch in comparable circumstances. I'm resolving this issue as WORKSFORME — with a readiness to re-open, should the symptoms recur.
worksforme -> closed
Recurred on Saturday, running OOo 3.0 for the first time as the administrator of a friend's iMac. 1. launch 2. allow checking for updates, opt to _not_ register later 3. observe a secondary application (JRE-related?) appear in Dock — and AFAIR that secondary application quit without error 4. wait maybe half an hour for OOo start centre to appear — start centre fails to appear 5. opt to force quit — force quit fails 6. opt again and again to force quit — force quit fails 7. in Terminal, command sudo kill -9 {PID of process relating to OOo)
> 3. observe a secondary application (JRE-related?) appear in Dock > > — and AFAIR that secondary application quit without error > > 4. wait maybe half an hour for OOo start centre to appear > > — start centre fails to appear Echoes of issue 98992, > OOo stops responding indefinitely following appearance of JREProperties
Closed