Apache OpenOffice (AOO) Bugzilla – Issue 7012
Crash upon startup
Last modified: 2003-03-11 17:55:16 UTC
After every reboot, when I run OpenOffice as user, the window frame is displayed, but the application terminates after a few seconds, without filling in the window (I can see everything thru it). When I run the program as root first and then as user, everything is fine until the next reboot. I don't see any directories or files with wrong permissions and I tried copying the system libdb-3.2.so over the one that comes with OpenOffice, but that doesn't change anything. I don't know how I can find out what might cause it to crash.
I have something similar happen on my system. Every so often (like the first time in the morning I try to bring up OO) when I select swriter from the Gnome Favorites->OpenOffice->Swriter menu the frame comes up stays up for a few seconds then goes away. The second time I do it it works. I am running as a normal non-root user. OO is installed as a network install. I'm looking in .xsession-errors for any output, but the only output is "SIOCGIFADDR got '0:0:0:0:0:0'" which comes out a random number of times whether swriter works or not.
Almost the same story. By clicking the OO icon in the panel I get the splash screen, then the frame for a few seconds and then nothing else. Trying again it won't work either. BUT if I click the icon of a document and then select soffice as the application to open it, it works. I'm working with Debian3 and GNome1.4 installed in a Toshiba Satellite 2540CDT with 128Mb RAM. OO is installed ynder /home/[user]/ as explained in the instructions.
Remco, this is probably issue 4494. I'm marking it as a duplicate of issue 4494. *** This issue has been marked as a duplicate of 4494 ***
As mentioned on the qa dev list on March 5th I will close all resolved duplicate issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified.
As mentioned on the qa dev list on March 5th I will close all resolved duplicate issues. Please see this posting for details.