Installing the OO.org 2.4 packages on F9 beta, I get this message when starting:
$ /opt/OOH680_m12/program/soffice Gtk-Message: Failed to load module "gnomebreakpad": /opt/OOH680_m12/program/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by /usr/lib/bug-buddy/libbreakpad.so.0)
OOo then starts and seems to run ok, but it will not run from a desktop launcher using that same command, I presume because bug-buddy can't be started.
I don't know what the Fedora policy is here: does it matter at this point whether a third-party package isn't starting cleanly? Nor do I understand the message well enough to decide who to report it to.
It seems that OOo uses it's own libstdc++ which is not compatible with gnomebreakpad, but I've not found a way to have gnomebreakpad look elsewhere for that library.
Any suggestions if/where to file a report, and/or how to workaround the problem?
<Joe
Joe Smith wrote:
Installing the OO.org 2.4 packages on F9 beta, I get this message when starting:
$ /opt/OOH680_m12/program/soffice Gtk-Message: Failed to load module "gnomebreakpad": /opt/OOH680_m12/program/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by /usr/lib/bug-buddy/libbreakpad.so.0)
OOo then starts and seems to run ok, but it will not run from a desktop launcher using that same command, I presume because bug-buddy can't be started.
I don't know what the Fedora policy is here: does it matter at this point whether a third-party package isn't starting cleanly? Nor do I understand the message well enough to decide who to report it to.
It seems that OOo uses it's own libstdc++ which is not compatible with gnomebreakpad, but I've not found a way to have gnomebreakpad look elsewhere for that library.
yum install libstdc++ The error is missing the libraries provided by that compatibility package, it may work fine when you've got it.
Andrew Farris wrote:
Joe Smith wrote:
It seems that OOo uses it's own libstdc++ which is not compatible with
Heh, sorry nevermind my prior mail I totally overlooked that its trying to pull the lib from /opt.
gnomebreakpad, but I've not found a way to have gnomebreakpad look elsewhere for that library.
yum install libstdc++ The error is missing the libraries provided by that compatibility package, it may work fine when you've got it.
Joe Smith wrote:
Installing the OO.org 2.4 packages on F9 beta
While I've already gotten interested in this (lol) why are you installing this anyway? You are aware that what is in f9 is a release candidate of 2.4 from mar 16 and will probably get bumped to full 2.4 within a week or so after the release freeze right?
Andrew Farris wrote:
Joe Smith wrote:
Installing the OO.org 2.4 packages on F9 beta
While I've already gotten interested in this (lol) why are you installing this anyway? You are aware that what is in f9 is a release candidate of 2.4 from mar 16 and will probably get bumped to full 2.4 within a week or so after the release freeze right?
I try to do some support on the OOo forums, so it's very important to have the OO.org build installed for testing.
Fedora's OOo builds are generally very very solid, but they are different from the OO.org builds at certain points. The OO.org build is a reference point for the 'standard' behavior across different distributions.
I like to have both, as the Fedora builds usually have better integration (e.g. with gstreamer, although this seems borked ATM), so it's often useful to compare the two builds.
<Joe
Joe Smith wrote:
Andrew Farris wrote:
Joe Smith wrote:
Installing the OO.org 2.4 packages on F9 beta
While I've already gotten interested in this (lol) why are you installing this anyway? You are aware that what is in f9 is a release candidate of 2.4 from mar 16 and will probably get bumped to full 2.4 within a week or so after the release freeze right?
I try to do some support on the OOo forums, so it's very important to have the OO.org build installed for testing.
Ordinarily, when one has a problem with software acquired directly from a third party, it's best to go to that third party for help getting it going.
In this case, it's not reasonable to expect a lot of expertise here, on installing and using OOo acquired directly from OpenOffice.Org.
Fedora's OOo builds are generally very very solid, but they are different from the OO.org builds at certain points. The OO.org build is a reference point for the 'standard' behavior across different distributions.
I like to have both, as the Fedora builds usually have better integration (e.g. with gstreamer, although this seems borked ATM), so it's often useful to compare the two builds.
John Summerfield wrote:
... Ordinarily, when one has a problem with software acquired directly from a third party, it's best to go to that third party for help getting it going.
In this case, it's not reasonable to expect a lot of expertise here, on installing and using OOo acquired directly from OpenOffice.Org.
Sure, except it also seems unlikely that the OOo people are going to know/care about problems running bug-buddy, in a beta release environment.
If someone can explain clearly to me what the problem is, and how OOo might look to fix it, I'll report it upstream.
On the theory that the libstdc++ shipping with OOo is not compatible with libbreakpad, I tried fiddling with LD_LOAD_LIBRARY in the OOo startup script, but without success.
So I still don't have a clear idea what to report to OOo is the actual problem here.
Maybe it will shake out in the updates leading to F9 release, but it's going to be a bit of a mess if F9 final doesn't run the OO.org download.
<Joe
Joe Smith wrote:
On the theory that the libstdc++ shipping with OOo is not compatible with libbreakpad, I tried fiddling with LD_LOAD_LIBRARY in the OOo startup script, but without success.
I'm not sure what the exact problem is but a big 'gotcha' is the switch to gcc 4.3 in rawhide which I'm pretty sure ooo upstream is not compiled with, and it could definitely effect your bug.
Andrew Farris wrote:
Joe Smith wrote:
On the theory that the libstdc++ shipping with OOo is not compatible with libbreakpad, I tried fiddling with LD_LOAD_LIBRARY in the OOo startup script, but without success.
I'm not sure what the exact problem is but a big 'gotcha' is the switch to gcc 4.3 in rawhide which I'm pretty sure ooo upstream is not compiled with, and it could definitely effect your bug.
Excellent point; I forgot about the compiler change. That would explain it.
Is there any way to disable bug-buddy for a particular app? It really doesn't make much sense to use bug-buddy for a third-party app anyway, right? It's not likely to have proper debug info, and the report doesn't need to go to Fedora.
Would it not make the most sense if OO.org could just configure their package to not use bug-buddy?
<Joe
Here are two solutions that worked for me: "Fix OpenOffice.org crashing" [1]
Links: ------ [1] http://www.oooninja.com/2008/08/irony-of-bug-buddy.html
-
Andrew Farris -
Joe Smith -
John Summerfield -
potat0