Apache OpenOffice (AOO) Bugzilla – Issue 5945
Open Office crashes silently on startup
Last modified: 2003-09-08 16:56:16 UTC
when starting openoffice, it will crash silently if left alone for a couple of seconds. if Ctl-O is pressed (open file) it stays open without crashing. the output when run in a terminal is... # /usr/local/openoffice1.0$ ./soffice sh: /usr/sbin/lpc: No such file or directory sh: lpc: command not found sh: lpstat: command not found .. and then the program crashes (i dont have a printer so i dont have lpd installed). If I restart it again, it sometimes stays up. On the third restart & subsequent restarts, it stays up & doesnt crash. Im using Debian Woody on a toshiba laptop x86 PIII, 128MB ram X, 4.1.0.1 OpenOffice 1.0.0
I'm having the same issue with both StarOffice 6.0 Final and OpenOffice.org 1.0, on a machine with the same amount of memory. It seems to be related to the amount of swap that OpenOffice.org/StarOffice has to use to open. If more than a meg of swap are used to open the program, it crashes. This issue does NOT occur on machines with 256 meg of memory. My platform: Red Hat 7.2 - 2.4.9-34 kernel Toshiba Tecra 8100 PIII 450 and 128 megs of memory This has also duplicated on a Dell Latitude LS with PIII 500, 128 meg of memory, and Red Hat 7.2 - 2.4.9-31 kernel, and several Dell Latitude CPx laptops with similar specs. In all cases, using 256 megs of memory fixes the issue, regardless of thr system load.
When you say *crash*, does it appear, and then disappear *without* any actual core dump ? Are you using gnome ?. If those are true then I would guess that this is issue 4494. Give the suggestions there a try. The machines seem a little high spec to be completely confident that its a duplicate. http://www.openoffice.org/issues/show_bug.cgi?id=4494
Caolan, Yes, bug 4494 does seem to fit my issue, thanks! The workaround also seems to work for me. I'm betting that this one is a duplicate of that bug. I would be interested to know if the original reporter was using GNOME also.
Just so that everybody is absolutely sure that it isn't a memory problem, I'd like to point out that I have 64MB RAM and 24MB of swap. I can run Mozilla 1.* and OOo 1.0.0 at the same time. So, I'm sure that memory isn't an issue, unless they are running something else that hogs a lot of memory.
Look like it's the Gnome SESSION_MANAGER issue. Marking as a dup. *** 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.