Bug 67495

I can confirm this bug. It exhibits the same symptoms here, on a system updated
to Raw Hide 20020627 (i.e. today's packages). I switched to the Raw Hide OO RPM
only this week and it never worked for me; before that I installed the official
builds from OO's site, which had never given me problems. Thus I can't confirm
or deny that GNOME2 might be at fault.

Initially, I had problems with fonts, or so I thought. chkfontpath reported a
bogus empty line in the font path. I fixed that and made sure that the font
server sees OO's OpenSymbol font, but it only seemed to postpone the crash a
bit.

For what it's worth, here are the last lines from the output of the command
"strace ooffice":

open("/usr/lib/openoffice/program/libi18n641li.so", O_RDONLY) = 13
read(13, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0P!\1\000"..., 1024) = 1024
fstat64(13, {st_mode=S_IFREG|0755, st_size=841160, ...}) = 0
old_mmap(NULL, 784784, PROT_READ|PROT_EXEC, MAP_PRIVATE, 13, 0) = 0x462ab000
mprotect(0x462d5000, 612752, PROT_NONE) = 0
old_mmap(0x462d5000, 614400, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 13,
0x29000) = 0x462d5000
close(13)                               = 0
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
kill(26003, SIGABRT)                    = 0
--- SIGABRT (Aborted) ---
rt_sigaction(SIGABRT, {SIG_DFL}, NULL, 8) = 0
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
kill(26003, SIGABRT)                    = 0
--- SIGABRT (Aborted) ---
+++ killed by SIGABRT +++

Quick workaround: Rebuild the package disabling the application of 
"openoffice-1.0-braindamage.patch". 

*** Bug 67868 has been marked as a duplicate of this bug. ***

Sopwith: This is a beehive problem. The fixed package 
(porkchop:~brosenkr/openoffice-1.0.0-4.src.rpm) builds perfectly outside of 
beehive (both as root and as user), but fails when in beehive. 
 
Please take a look at it.

I need build logs or something that points at beehive as the problem. If you
could save those it would be helpful. I can't do anything at all about the
problem otherwise - I'm not going to sit through an OO build just to get logs :)

*** Bug 67928 has been marked as a duplicate of this bug. ***

*** Bug 68081 has been marked as a duplicate of this bug. ***

I rebuilt from the src.rpm both with and without the
'openoffice-1.0-braindamage.patch' on a freshly installed Limbo box. Neither
resulted in a working OpenOffice.

The OpenOffice.org binaries from the OO website don't work either, but they
break  a little further in, with a mysterious error dialog. Debugging shows
threads dying without leaving any indication why.

*** Bug 68138 has been marked as a duplicate of this bug. ***

My install is missing several files from  /usr/lib/openoffice/user/config/
that appear to be in the package list ('rpm -qlp openoffice*.rpm' shows them)
so the initial user config skips some .so[cedh] files.

Running oo* shows the splash screen athen exits with
"SIOCGIFADDR got 00:00:00:00:00:00"
That looks like a MAC address, but that box is ppp only,
no NIC.

rpm -V reported no problems.
I reinstalled openoffice
using --replacepkgs and the missing files got are now there.
I wonder how many other packages are not complete.
(re reinstalled mozilla and it fixed a menyu problem)
Why didn't -V catch the missing files?

Still, now the frist run doesn't report missing files,
but openoffice exits with the same SICCGIFADDR again.

Created attachment 64617 [details]
openoffice log

Maybe this will help. I have redirected the output from openoffice to a file.
Check the previous attachement.

OpenOffice version:
openoffice-1.0.0-4

*** Bug 68587 has been marked as a duplicate of this bug. ***

I've used gdb to debug the program, here is the
debug infomation:
------------------------------------------------
[chluo@LuoChong .openoffice]$ gdb /usr/local/OpenOffice.org1.0/program/soffice.bin
GNU gdb Red Hat Linux (5.1.92-3)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux"...
(gdb) run
Starting program: /usr/local/OpenOffice.org1.0/program/soffice.bin
[New Thread 1024 (LWP 13199)]
[New Thread 2049 (LWP 13200)]
[New Thread 1026 (LWP 13201)]
[New Thread 2051 (LWP 13202)]
[New Thread 3076 (LWP 13203)]
[New Thread 4101 (LWP 13206)]
Program received signal SIGBUS, Bus error.
[Switching to Thread 1024 (LWP 13199)]
0x47687834 in __bam_read_root ()
   from /usr/local/OpenOffice.org1.0/program/libdb-3.2.so
(gdb)
(gdb)
(gdb)
(gdb)
(gdb) continue
Continuing.

Program received signal SIGABRT, Aborted.
0x42027811 in kill () from /lib/i686/libc.so.6
(gdb)
(gdb) quit
The program is running.  Exit anyway? (y or n) y
[chluo@LuoChong .openoffice]$
----------------------------------------------------------

*** Bug 69030 has been marked as a duplicate of this bug. ***

*** Bug 68138 has been marked as a duplicate of this bug. ***

OpenOffice.org 1.0.1 has been released.
Is it usable in Redhat limbo?

Version 1.0.1 downloaded from www.openoffice.org doesn't work for me with limbo.
 openoffice-1.0.0-7.i386.rpm (and the associated i18n and libs rpms), new in
rawhide, does work for me.

Does that mean the guys of Redhat have solved the problem? 
That's a good news.
But my connection to internet is too slow, I can't afford to download those
three big files. Perhaps I have to wait until the release of Redhat 8.0 (or
7.4?) to enjoy working with openoffice. :-(

Hi, eveyone, I've found a way to solve the problem!
1. Install db3-3.2.9-4.i386.rpm from Redhat 7.2.
2. Use /usr/lib/libdb_cxx-3.2.so and /lib/libdb-3.2.so to replace the
corresponding file under /usr/local/OpenOffice.org1.0/program/.
3. start openoffice.
Then everything is OK!

openoffice-1.0.0-7 still does not start up
$ ooffice
Checking for existing user installation ...   ...   NOT FOUND
Performing first-time installation for user ...   /usr/bin/ooffice: line 40:
20278 Segmentation fault      /usr/lib/openoffice/program/setup
-R:/etc/openoffice/autoresponse.conf
...   FAILED

I didn't test the openoffice-1.0.0-4.i386.rpm shipped with redhat limbo,
instead I've tested the one from www.openoffice.org.

Just another data point.   
The Limbo RPMs did not work for me either. I tried the new OO-1.0.1   
binaries form www.openoffice.org on my Limbo installation to no avail.  
I got the SIOCGIFADDR message and then nothing (no NIC here). Just  
removing the libdb-3.2.so and libdb_cxx-3.2.so libraries from  
/usr/local/OpenOffice.org1.0/program did the trick. The SIOCGIFADDR  
message is still here.  

1) those who are seeing hangs or crashes in libdb with OOo binaries, it is
   because they have miscompiled libdb-3.2.so (calls mmap64 with random
   upper 32-bits of offset) - simply remove libdb-3.2.so and let it use the
   system one
2) SIOCGIFADDR got 00:00:00:00:00:00 at least from my reading of the code
   should definitely not be a problem - it just means OOo will use random
   6 bytes for UUID instead of ethernet address
3) to askalis.gr: are you sure you have
   a) /proc mounted
   b) /etc/mtab present
   ? If yes, can you ulimit -c unlimited and attach gdb backtrace?

Yes, /proc is mounted, /etc/mtab exists.  gdb backtrace attached below.

Created attachment 66186 [details]
gdb backet

Created attachment 66187 [details]
gdb backtrace

The package openoffice-1.0.0-7.src.rpm has been tested internaly. It works and
should become available with next public beta.

If development agrees, this bug can be closed.

Version in second limbo worked after a clean install.