Summary: | Rebuilding OpenOffice fails with segfault | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stuart Shelton <srcshelton> |
Component: | Current packages | Assignee: | Gentoo Office Team <office> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Build output as seen on console
xtrace output of failed openoffice-1.1.0-r2 build openoffice-1.1.0-r2 strace of hung splash screen Another strace of failed openoffice binary emerge info |
Description
Stuart Shelton
2004-02-04 02:49:05 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.
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.
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...
Created attachment 24929 [details]
Another strace of failed openoffice binary
BTW, s/crashdebug/crash_report/g in the above :) 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 ;-) 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? Created attachment 25006 [details]
emerge info
As requested...
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. 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! Closing, because I can now rebuild OpenOffice successfully. |