Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 40362 - Rebuilding OpenOffice fails with segfault
Summary: Rebuilding OpenOffice fails with segfault
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Office Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-04 02:49 UTC by Stuart Shelton
Modified: 2004-07-12 11:07 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
Build output as seen on console (ooe1.log.bz2,725.21 KB, text/plain)
2004-02-04 02:51 UTC, Stuart Shelton
Details
xtrace output of failed openoffice-1.1.0-r2 build (ooe2.log.bz2,128.38 KB, text/plain)
2004-02-04 02:53 UTC, Stuart Shelton
Details
openoffice-1.1.0-r2 strace of hung splash screen (soffice.bin.strace.bz2,61.52 KB, text/plain)
2004-02-04 02:55 UTC, Stuart Shelton
Details
Another strace of failed openoffice binary (soffice.bin.strace.2.bz2,63.41 KB, text/plain)
2004-02-04 02:58 UTC, Stuart Shelton
Details
emerge info (emerge.info,1.97 KB, text/plain)
2004-02-05 06:40 UTC, Stuart Shelton
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stuart Shelton 2004-02-04 02:49:05 UTC
I had openoffice-1.1.0-r2 installed and working fine, but it broke (progress splashbar fills to about 1/3, then stops permanently) after I installed Sun's JDK.  Easily fixed by setting the Blackdown JDK as default.

Some time later, OO broke again in exactly the same way, but I hadn't changed anything (other than doing x86 world updates - including glibc).

I couldn't find the problem, so decided to rebuild OO again.  However, I had a range of problems:  The standard openoffice-1.1.0-r2 ebuild compiled everything and got as far as launching the installer under xvfb with the autoresponse file, but this segfaulted.  After several attempts, I tried the openoffice-ximian-1.1.49 package - which did compile and install.  However running anything other than "ooffice" presented the familiar "freeze at 1/3" problem, whilst running ooffice initialised and opened a correct-looking blank MDI parent window with OO menus.  Unfortunately, any attempt to open these menus or to use any keyboard accelerators to access menu functions also resulted in the program freezing.

I'll attach my build logs and a couple of straces, incase that helps.

make.conf flags: CFLAGS="-O2 -march=pentium4 -mfpmath=sse -msse2 -fprefetch-loop-arrays -pipe" (also tried without prefetch-loop-arrays: no difference)
Relevant keywords: USE="gnome kde"

Output of java-config -L:
[sun-jdk-1.4.2.03] "Sun JDK 1.4.2.03" (/etc/env.d/java/20sun-jdk-1.4.2.03)
[kaffe-1.0.7_rc1] "Kaffe 1.0.7_rc1" (/etc/env.d/java/20kaffe-1.0.7_rc1)
[sun-j2sdk-1.4.1] "Sun JDK 1.4.1" (/etc/env.d/java/20sun-j2sdk-1.4.1)
[blackdown-jdk-1.4.1] "Blackdown JDK 1.4.1" (/etc/env.d/java/20blackdown-jdk-1.4.1) *

Output of java-config -p:
/opt/blackdown-jdk-1.4.1/jre/lib/rt.jar:.


Can I supply anything else of use?

TIA,

    Stuart

Reproducible: Always
Steps to Reproduce:
(Attempt to) Compile openoffice-ximian-1.1.49 or openoffice-1.1.0-r2
Actual Results:  
Compilation successed, but then compiled binary failed on installation or on
invokation.



I also noticed that there was an error about gtk, and the crashdebug binary
wasn't seeming to be built - could this be another gtk/gtk2 compatibility problem?:

"
WARNING! Project(s):
gtk

not found and couldn't be built. Correct build.lsts.
"

I currently have the binary openoffice ebuild installed, which works absolutely
fine.
Comment 1 Stuart Shelton 2004-02-04 02:51:24 UTC
Created attachment 24926 [details]
Build output as seen on console

Build output showing openoffice-1.1.0-r2 apparently succeeding - but actually,
the installer has segfaulted.
Comment 2 Stuart Shelton 2004-02-04 02:53:00 UTC
Created attachment 24927 [details]
xtrace output of failed openoffice-1.1.0-r2 build

More detail of failed build - shell xtrace output showing operations performed.
Comment 3 Stuart Shelton 2004-02-04 02:55:57 UTC
Created attachment 24928 [details]
openoffice-1.1.0-r2 strace of hung splash screen


Once soffice is launched, the splash screen freezes at about 1/3 (and there is
an error reported on the console about not being able to find the crashdebug
utility).  This is the trace...
Comment 4 Stuart Shelton 2004-02-04 02:58:00 UTC
Created attachment 24929 [details]
Another strace of failed openoffice binary
Comment 5 Stuart Shelton 2004-02-04 02:58:55 UTC
BTW, s/crashdebug/crash_report/g in the above :)
Comment 6 Andreas Proschofsky (RETIRED) gentoo-dev 2004-02-05 03:55:27 UTC
As always: Please provide the output of emerge info.

Some quick notes: The gtk error is non-harmful, so just forget about it ;-)

And please don't attach bzipped files to the bug, or at least mark them as binary file and not text/plain makes reading them easier ;-)
Comment 7 Stuart Shelton 2004-02-05 06:40:06 UTC
Okay, sorry.  I was using Gentoo (with less & lesspipe) to look at the traces, so the bzipped files were automatically decompressed.  D'oh!

I'm attaching the emerge info output (which *is* uncompressed) now...

P.S. Fair enough on the "gtk" thing - but is this why crash_report seems to always be missing?
Comment 8 Stuart Shelton 2004-02-05 06:40:48 UTC
Created attachment 25006 [details]
emerge info


As requested...
Comment 9 Paul de Vrieze (RETIRED) gentoo-dev 2004-02-05 12:22:05 UTC
Basically the crashreporter is used to send crash data to the openoffice project. However as it is a homebrewn version of openoffice, this data would be useless to them as it would still not allow recognizing the problem. Further it is not really clear to add gtk support even if we wanted it. The warning is something we just have to live with.
Comment 10 Stuart Shelton 2004-02-06 01:10:31 UTC
Okay - that's a lot clearer.  Thanks.

Any ideas yet about the main problem, though?
If there's anything else I can supply to help, just let me know.

Cheers!
Comment 11 Stuart Shelton 2004-07-12 11:07:57 UTC
Closing, because I can now rebuild OpenOffice successfully.