Closed Bug 244189 Opened 21 years ago Closed 20 years ago

Failed to install and initialize due to no libstdc++.so.5

Categories

(Core Graveyard :: Talkback Client, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: marko.kohtala, Assigned: namachi)

References

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040514 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040514 Talkback seems to depend on libstdc++.so.5. This is newer than what is available on latest stable Debian distro. Reproducible: Always Steps to Reproduce: 1. Install using mozilla-installer 2. Run Actual Results: During mozilla-installer I get this several times: nsNativeComponentLoader: SelfRegisterDll(talkback.so) Load FAILED with error: libstdc++.so.5: cannot open shared object file: No such file or directory During startup of mozilla, I get this "(QFA)Talkback error: Can't initialize.". I Expected Results: No newer libstdc++ required. I run Debian 3.0 and have libstdc++.so.3.
so it looks like talkback installations might get more complex if we try to support a wide variety of linux distros...
mozilla itself avoids this problem by statically linking that library, afaik
And when distros start shipping gcc 3.4 you'll have to deal with libstdc++.so.6.
*** Bug 246513 has been marked as a duplicate of this bug. ***
I'm using Debian 3.0 (Woody) with libstdc++.so.3.0.4 . QFA can run with this version of libstdc++ too, after some hacking: $ ln -s /usr/lib/libstdc++.so.3 libstdc++.so.5 $ export LD_LIBRARY_PATH=. $ mozilla -splash Now the error message disappears. The QFA is invoked only when something goes wrong. This can be simulated sending a SIGSEGV signal to mozilla-bin process: $ killall -11 mozilla-bin and the QFA starts (do NOT send this bug report this time, because it is only a simulation!)
*** Bug 258871 has been marked as a duplicate of this bug. ***
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.