Apache OpenOffice (AOO) Bugzilla – Issue 4494
All Apps exit after start
Last modified: 2005-08-26 14:46:31 UTC
I installed V1.0.0 on my linux box (kernel 2.2.19/2.4.19-pre6). The Installer says everything went OK, but I cant start any of the Apps. What happens is that a short time after start i see the main window of the app started, but it will exit immediately. there is no core file of any log entry indicating a problem, so i really dont know what to make out of this, but it looks bad :-(
Maybe the same problem as 4475.
I too have this problem under GNOME. Most of the time (under gnome), as soon as the OO.o Writer window opens, it disappears with no errors. Sometimes it will stay open and I can use OO.o. Debian GNU/Linux sid running kernel 2.4.18. This does NOT happen under icewm-- it is very stable. I noticed another post regarding this problem after an upgrade to Ximian gnome-- perhaps the problem lies in (newer) gnome libraries?
I am using GNOME V1.4, X 4.0.1 FYI since it seems that this is more relevant than the kernel (it looks the same under both kernels). And, I didn't know what component give it, so i assigned it to the UI which was the most intuitive thing to do ...
same here on Debian/woody kernel 2.4.19-pre7 Doesn't happen when I start simpress first, but closing on Ooo app will kill all other windows.
I have seen similar bugreports with these sypmtoms: It only happens under GNOME, and Opera fails too. I was given information from the Opera newsgroup - maybe you can try this: create ~/.gnomerc with this line: exec /usr/bin/gnome-session --suicide-delay=0 --purge-delay=0 --warn-delay=0 And restart your window manager. Does that help? (The Debian user who reported this said he changed /etc/gdm/Sessions/Gnome, not ~/.gnomerc.)
OK, it appears it is only --purge-delay that needs changing: exec /usr/bin/gnome-session --purge-delay=0
*** Issue 4470 has been marked as a duplicate of this issue. ***
I wonder if there is a connection to the gnome "save yourself" message ? That can cause glitches for some applications, if so, then adding unset SESSION_MANAGER to the swriter/scalc/sdraw/simpress/... scripts might be a workaround.
Yes! unset SESSION_MANAGER works :) You only need to do this in the soffice script - everything else comes through here anyway (except spadmin)
*** Issue 4808 has been marked as a duplicate of this issue. ***
cmc->os: If the session manager thing is truly the problem, then maybe this is something for gsl to handle.
*** Issue 4236 has been marked as a duplicate of this issue. ***
There is a related bug in the Gnome bugzilla about this. http://bugzilla.gnome.org/show_bug.cgi?id=81343 The reporter (who found the same problem when using sdtprocess) said: "tracing through the Xserver to see why it was closing the connection - it turns out to simply be honoring an XKillClient() from gnome-smproxy. You can see this yourself by running gnome-smproxy in a debugger, setting a breakpoint on XKillClient, and then running sdtprocess. After a while, you'll see the breakpoint is hit - as soon as you hit continue, the sdtprocess will die." So, it looks like it's a problem with gnome-smproxy. OOo has to use this because it does not support X11R6 session management, only R5. Is it worth considering changing that session management to support the X11R6 protocol to fix this?
cmc->cp: I bet this is a gnome bug, but you know anything about session management under gnome.
OOo actually supports the newer session management (see the code in gsl/vcl/unx/source/app/sm.cxx). It would seem that OOo just does not start soon enough for the gnome-session. Probably setting the --purge-delay to a value high enought should suffice. The only chance to fix the problem on office side would be to decrease startup time - which would certainly be good, but this is an ongonig task we try anyway :-) Unless someone has more information on this i think we can close this issue.
cp->cmc: I don't see any other option. Any tricks to fool the gnome session ?
cmc->cp: I certainly haven't a clue. Is it not possible to be in a position to handle session management during the time from when we draw the splashscreen to when we are truly started ? Maybe the gnome people will come up with some recommendations. A pity there isn't a way to link two the bugzillas together to get mutual updates on something on this. Either way I doubt my ownership of this makes a lot of sense :-), might as well belong to you in case its reopened with new info.
*** Issue 5099 has been marked as a duplicate of this issue. ***
*** Issue 4709 has been marked as a duplicate of this issue. ***
Hey. So 81343 in GNOME's bugzilla was a slightly different issue. Out of curiosity, is openoffice's session management done with WM_SAVE_YOURSELF command or XMSP? WM_SAVE_YOURSELF is deprecated. We could length the purge time, but how long is long enough ? Its 30 seconds at the moment.
*** Issue 5522 has been marked as a duplicate of this issue. ***
*** Issue 5632 has been marked as a duplicate of this issue. ***
Mark: Ooo does XSMP as well as WM_SAVE_YOURSELF to have session management on older platforms (e.g. CDE) and newer ones (GNOME, KDE).
*** Issue 5684 has been marked as a duplicate of this issue. ***
*** Issue 5799 has been marked as a duplicate of this issue. ***
*** Issue 5926 has been marked as a duplicate of this issue. ***
I'm getting the exact same symptoms as you guys, running GNOME1.4, Sawfish on Deb Sid 2.4.18, except my working workaround is to make sure /dev/dsp isn't locked up by xmms - as I am always playing music. The software only bombs when dsp is in use, never when not. Note - I don't use ESD
*** Issue 4200 has been marked as a duplicate of this issue. ***
Hi! issue 6291 should be marked as the same bug as this one. For RedHat7.3 users, if you "install everything" when installing RH7.3 , this problem is corrected automatically.
*** Issue 6291 has been marked as a duplicate of this issue. ***
I have been consistently hitting a similar(or the same) problem. I have two monitors hooked to my Solaris9 System. The two monitors have different drivers(m640 and PGX). When i start Openoffice 1.0 on my first monitor it works fine. But when i try to start OOo on my second monitor, I see the splash and then the writer opens and then dies immediately. This happens always. So aparantly OOo doesn't bode well with some frame buffer drivers. I am using CDE, So i would say the problem is not just with gnome.
I have the same symptoms, but unsetting session manager doesn't work. Here is my report: I just downloaded Ov1.0.1 and tried to run `./setup -net` so that I could install it. A window opened that showed a package with an progress bar filling up. It got to about 50% then disapeared. The entire screen flashed, like a window quickly opened then closed. After that setup exited with a status of 01. The only thing displayed on the command line is 'glibc version: 2.2.5' I've tried running `./setup -repair`, but that does the same thing. My envirnment currently looks like this (but I've tried different variations, especially with SESSION_MANAGER): PWD=/root/tmp/install OPENSSL_CONF=/root/.openssl.cnf http_proxy=http://localhost:8118/ XAUTHORITY=/home/devin/.Xauthority SESSION_MANAGER= CLASSPATH= GDMSESSION=Gnome ANT_HOME=/home/devin/local/ant GNOME_SESSION_NAME= USER=root LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.jpg=01;35:*.jpeg=01;35:*.png=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.mpg=01;35:*.mpeg=01;35:*.avi=01;35:*.fli=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.ogg=01;35:*.mp3=01;35: CVS_RSH=fsh MAIL=/home/devin/Maildir OLDPWD=/root/tmp LANG= HOST=elektrono.com JAVA_HOME= COLORTERM= DISPLAY=:0 LOGNAME=devin SHLVL=3 PILOTPORT=/dev/ircomm0 SSH_AGENT_PID=3955 PILOTRATE=115200 GDM_LANG= USERNAME=devin SHELL=/bin/bash HOME=/root SSH_AUTH_SOCK=/tmp/ssh-XXYznpo2/agent.3954 TERM=xterm PATH=/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/usr/local/sbin:/usr/sbin:/sbin:./ _=/usr/bin/env `uname -a` = "Linux elektrono 2.4.18 #1 Sat Jul 13 18:13:57 EDT 2002 i686 unknown" I am running Debian GNU/Linux 3.0, and I've tried the .deb of OOo, but that doesn't work either. Some versions of library dependencies: X11: 4.1.0 libc6: 2.2.5 If I install OOo another way (like with ./install or apt-get) then running the unpacked programs doesn't quite work. The widgets are huge and take up almost the whole screen individually. This is probally related.
*** Issue 6633 has been marked as a duplicate of this issue. ***
May I suggest that the start script only look at the executable name i.e. gnome-session not the whole path as it is not always located there. I am running Gnome2 built with Garnome and it is running from /usr/local/garnome/bin. Thanks.
*** Issue 7416 has been marked as a duplicate of this issue. ***
For the next version of Red Hat, I'm upping the purge delay for gnome-session to 5 minutes. Hopefully it won't take 5 minutes to start open office on any system where it's interesting to use it.
*** Issue 4827 has been marked as a duplicate of this issue. ***
*** Issue 6924 has been marked as a duplicate of this issue. ***
*** Issue 5945 has been marked as a duplicate of this issue. ***
*** Issue 7917 has been marked as a duplicate of this issue. ***
If unset SESSION_MANAGER doesn't work, look for the following in setup.log: error: RegistryItemAction::Execute() called I tracked this to Issue 6513 and renamed libdb-3.2.so in the the programs directory as hinted at in the discussion. This worked.
*** Issue 7012 has been marked as a duplicate of this issue. ***
ok, nothing we can do now. Has to be revised with the next vcl rework
*** Issue 10451 has been marked as a duplicate of this issue. ***
If the problem is related to the startup time, would it be possible to have a dummy window opened very fast (Stg like the welcome screen, but as soon as possible, and in the form of a window). Wether or not the bug comes from Gnome will not affect the opinion of basic users, so, we need a fix, even if it is a dirty workaround.
I just put out the release candidate gnome-session for our GNOME 2.2 release and in it I upped this purge timeout to 2 minutes. So I doubt you guys will be affected anymore ... In 2.4 we'll make this timeout configurable. We'll also notify the user and ask for confirmation before killing off any app. This all should have been done long before now.
This is fixed in the next 644 build anyway since ICE (and therefore SM) connections are now processed in a separate thread that is not dependent on the office startup
*** Issue 10768 has been marked as a duplicate of this issue. ***
*** Issue 12506 has been marked as a duplicate of this issue. ***
closed
I have recently come across this issue in 1.1.5rc3 on an old Debian 3.0 box. I notice that there seems to be a fix provided in the README file (headed "Problems During Program Startup on Gnome"). Of course I didn't read it until after I'd found this bug report. :-/ Would it be possible to include this fix as an option when OpenOffice is installed? Also I think this issue and issue 3448 are the same.