Apache OpenOffice (AOO) Bugzilla – Issue 5684
OpenOffice tries to close on startup
Last modified: 2003-03-11 17:54:22 UTC
Howdy; I've got a peculiar issue with both OpenOffice and StarOffice (1.0 and 6.0 respectively). This makes me think that it's an environment issue. Initially, I thought this was logo related (reference http://www.openoffice.org/servlets/ReadMsg?msgId=329389&listName=users) but it turns out I'd been hitting the crack pipe a bit too hard (it's not logo related, it was a flaw in my methodology). What appears to be the case is that *Office is trying to start up, and then it tries to close (presumably with some sort of File, Close). This is evidenced by it starting whatever application you want, and then immediately closing it. This is irrespective of whether it's a new or previous document. The way to hack around this issue is to be very quick with the key strokes. On startup, if you can get in there and enter some data into the application, it will ask you if you want to Save/Discard/Cancel. If you say Cancel, then it continues on happily, and you can open/save/whatever to your heart's content. I now believe I know why this is occuring; it appears to be a conflict in xscreensaver. I'm running: $ dpkg --list xscreensaver\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-==============-==============-============================================ ii xscreensaver 3.34-3 Automatic screensaver for X ii xscreensaver-g 3.34-3 GL(Mesa) screenhacks for xscreensaver ii xscreensaver-g 3.34-3 GNOME binaries for xscreensaver If I kill the daemon, then I can start *Office just fine. I am going to file a bug on xscreensaver for this as well, and reference this project issue. I've got a workaround, so it's hardly major or urgent, just damn annoying :) Cheers Richard
After looking at some emails on users@openoffice.org, it seems that it's possible to fix this by altering the $INSTALL/program/soffice script and adding: unset SESSION_MANAGER ...at any point. This has seemed, in my thusfar limited testing, to "fix" the problem. It'd be nice to know why this occurs - as it happens with both Star and Open Office suites, it could be something interesting that they're doing. Or it could be a feature of xscreensaver - questions, always questions.
IMHO duplicate to 4494
Yes, it's a duplicate. Chris *** 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.