Issue 8856 - Crashes on startup with "unrecoverable error" and dumps core
Summary: Crashes on startup with "unrecoverable error" and dumps core
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 1.0.1
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: centaur
QA Contact: issues@installation
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2002-10-30 21:49 UTC by centaur
Modified: 2003-03-13 10:17 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Core dump as described in summary (3.55 MB, application/octet-stream)
2002-10-30 21:56 UTC, centaur
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description centaur 2002-10-30 21:49:41 UTC
I just installed Open Office 1.0.1.  I am on an i686 running Red Hat 7.1 (all
updates available from RHN have been applied), kernel version 2.4.19.  When I
started the program for the first time with ~/OpenOffice.org1.0.1/soffice I got
the title screen, followed shortly by a dialog that said "An unrecoverable error
has occured".  After I click OK I get a core dump.  I'm not sure how to attach
the core dump directly, so I've made it available at the URL I filled in above -- 
http://www.netmagic.net/~centaur/core.9234.bz2
Comment 1 centaur 2002-10-30 21:56:23 UTC
Created attachment 3431 [details]
Core dump as described in summary
Comment 2 prgmgr 2002-10-31 00:27:48 UTC
Thank you for using and supporting OOo.

I have a few questions

Did you download OOo from the OpenOffice.org web site?

Does your system meet the minimum requirements listed in the 
readme.txt file?

What type of install did you perform?
Comment 3 prgmgr 2002-10-31 00:29:08 UTC
I hope I reassigned to the proper group.
Comment 4 centaur 2002-10-31 06:31:11 UTC
In answer to your questions:

Did you download OOo from the OpenOffice.org web site?

Yes, I used the mirror listed on the download page - the link is
http://sf1.mirror.openoffice.org/stable/1.0.1/OOo_1.0.1_LinuxIntel_install.tar.gz

Does your system meet the minimum requirements listed in the
readme.txt file?

I did not look at readme.txt, but my system meets the requirements for
linux as listed at
http://www.openoffice.org/dev_docs/source/sys_reqs.html
Specifically, I have Red Hat 7.1 running kernel version 2.4.19,
128 MB of physical RAM, 1+ GB of swap configured, and 2.5 GB of
available disk.  The glibc version is 2.2.90-26.  I am running gnome
with the sawfish window manager and I have an Nvidia Riva Ultra TNT 2
graphics card.

What type of install did you perform?

I followed the installation instructions listed at
http://www.openoffice.org/dev_docs/instructions.html#linux
and I installed it in /opt using the root login as suggested.  I then
ran the setup script as a non-privileged user.  Finally, I tried to
run the program and that's when I got the unrecoverable error followed
by a core dump.

When I have some time, I'll download the source and try building it
locally; maybe I'll have better luck that way.

Thanks,
Per Nystrom
Comment 5 centaur 2002-11-06 18:57:15 UTC
Since I figured out how to attach it to this bug, I've removed the
core dump from the URL I originally listed.

I tried to build it from the source, but got other errors during
compile time that I haven't chased after yet.

I also reinstalled the whole thing from scratch, but the behavior is
still exactly the same: the installation and setup go flawlessly, but
the first time I run ~/OpenOffice.org1.0.1/soffice I get the startup
screen followed shortly by the unrecoverable error dialog.

I've tried running strace on the executable, but I haven't yet found
any obvious problems in the output.
Comment 6 Olaf Felka 2002-11-07 12:32:27 UTC
Looks for me like the "gnome/sawfish" problem. Please have a look at
issue 4494.
Comment 7 centaur 2002-11-07 19:56:34 UTC
I've read issue 4494 thoroughly, and tried all the suggested
workarounds (except upgrading to Red Hat 7.3 and installing
everything; this is a bit extreme for me!).  I've had no joy
whatsoever.  The behavior remains the same no matter what.  So future
readers can avoid flipping between the two bugs, here are the
workarounds I found for issue 4494:

1. create a ~/.gnomerc file containing this line:
     /usr/bin/gnome-session --suicide-delay=0 --purge-delay=0 \
     --warn-delay=0
   and then restart the windows manager.
   Later on it was mentioned that only --purge-delay=0 was needed.

2. unset SESSSION_MANAGER in the soffice startup script.

3. Make sure /dev/dsp is not locked by xmms.

I've tried all these suggestions separately and in combination, and I
have not been running xmms during any of my attempts to start soffice.  

I will check to see if there are newer versions of gnome and/or
sawfish out there for me, it's at least something to chase while we
ponder what to try next.

Thanks,
Per Nystrom
Comment 8 centaur 2002-11-12 22:37:04 UTC
Well, I gave up on trying to upgrade just gnome/sawfish, and bit the
bullet and upgraded to Red Hat 8.0.  Even after doing that, the
installation from OOo_1.0.1_LinuxIntel_install.tar.gz *still* resulted
in a crash with unrecoverable error when trying to run soffice.

However, I then obtained the OO rpm packages for Red Hat 8.0 and
installed them:
$ rpm -qa openoff*
openoffice-1.0.1-8
openoffice-i18n-1.0.1-8
openoffice-libs-1.0.1-8
...and it finally works!

So as far as I'm concerned, the problem is solved.  It's still
probably worth looking into why the tar.gz distribution won't work on
Red Hat, but the rpm does; especially if there are others having the
same trouble -- or maybe it's just some peculiarity with my system.
Comment 9 prgmgr 2002-11-14 17:04:23 UTC
Thanks for the update.

It is a known issue in regards to the tarball binaries not working
with RH 8.0.

That should be addressed in the next release.
Comment 10 michael.bemmer 2003-03-13 09:41:54 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.
Comment 11 michael.bemmer 2003-03-13 10:17:30 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.