Apache OpenOffice (AOO) Bugzilla – Issue 4709
When starting the first time in a session, Writer crashes seconds after starting.
Last modified: 2003-09-08 16:56:16 UTC
This happens EVERY TIME, when starting as a normal user. Debian Linux, GNOME 1.2, XFree 4.1. Starting also takes quite a while on my Celeron 466 MHz/384 MB. When I restart OOo Writer directly after the crash it will run and work fine. I have tried as root and it worked without crashing. But I didn't try that often, because usually I don't do office work as root. I have read Issue#: 4430, Issue#: 4470 and seen the remark about this problem with the de_CH dictionary but this problem occurs, too, if de_CH is not present.
After installing the OpenOffice QuickStarter Applet the problem dissappears (it reappears if the QuickStarter Applet is not used).
Can you check issue 4494? This may be a duplicate
Hi Chris. Somehow my answer to your request if this maybe a duplicate seems to have got lost? Well, what I wrote was basically that i thought, no, this was no duplicate, because OOo would work fine on 2nd (and consequent) starts. In the meanwhile I had a severe crash involving my user profile (affecting several programs' settings) and after some grave problems with repair of OOo settings had to reinstall OOo. With the new profile OOo seems not to crash at first boot, (at least not yet). So I checked the settings and found a difference in the settings for language support (linguistics? I am using the German version of OOo): I found that I had an entry for Italian in the dictionaries.lst but no Italian dictionary installed (silly me). This is now removed. OOo stars a lot faster than before and, as said, seems not to crash. So, possibly the crash was due to the wrong entry in the directories.lst. I will try to reproduce the problem/verify as soon as I find time. Regards Andreas
Hello, I have almost an identical setup to the original poster. debian 3.0, kernel 2.4.18. my swriter crashes the first time I startup, w/o fail. sometimes it will crash several times. It started doing this in the 64x releases. when I upgraded to 1.0, it seemed to go away for a while, and now it's back with a vengance. I've tried unsetting my SESSION_MANAGER (as mentioned in a linked bug), but I won't be able to tell if that's the issue until tommorrow. I can provide more detailed info if someone will tell me how to get a proper debug (strace doesn't seem to give very usefull information). Thanks.
Hello again. Sadly, the crash at first start has come back to me, too. But it is still only the first start that crashes. Also, possibly connected to this, one document window will always immediately restore when you minimize it - until you close down OOo once and then restart. I still have no idea how to get a pattern and more debug info out of this. So I, too, would be happy about hints how to provide required debug information. Regards Andreas
Chris->Andreas: > Well, what I wrote was basically that i thought, no, > this was no duplicate, because OOo would work fine on 2nd (and > consequent) starts No, this is perfectly possible. The problem in issue 4494 is that the Gnome session manager kills OOo because it takes too long to start. The second time OOo starts, it will probably start faster because of cached files, etc. You don't seem to have actually tried the workarounds in the issue I pointed to. Please do the following and see if the problem still persists: unset SESSION_MANAGER soffice (or openoffice if you're using the .deb) Chris
the unset SESSION_MANAGER seems to be working for me. Since I've added that to the startup, I haven't had soffice crash on me. I haven't been using it a bunch, but the 5-6 times I have, things have been fine. Thanks. -Peter
Lets call it a duplicate then *** 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.