Closed
Bug 176464
Opened 23 years ago
Closed 23 years ago
Mozilla crashes on loading the Java plugin
Categories
(Core Graveyard :: Java: OJI, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: graham.knap, Assigned: joe.chou)
References
()
Details
(Keywords: crash)
As soon as I attempt to navigate to the above URL, Mozilla closes. Here's what
gets dumped to the console.
java_vm: relocation error: /usr/local/mozilla/plugins/java2/lib/i386/libjava.so:
symbol __libc_wait, version GLIBC_2.0 not defined in file libc.so.6 with link
time reference
INTERNAL ERROR on Browser End: Could not read ack from browser
System error?:: Resource temporarily unavailable
The exit code is 0377.
I am guessing that this problem has something to do with my system C libraries.
The browser version doesn't seem to matter; I've tried 1.1b, 1.2a and 1.2b. The
java plugin is 1.3.0_02, which is what Mozilla automatically downloads when you
visit a Java-enabled webpage.
"apt-cache show libc6" tells me that I have glibc2.3.1.
To stop Mozilla crashing, for now, I am going to disable Java. :-(
If you need any further configuration info etc., I'd be happy to help.
Comment 1•23 years ago
|
||
never a blocker.
Reporter:
Have you symlinked the plugin ?
Do you compile yourself with gcc3.x or do you use builds from mozilla.org ?
Severity: blocker → critical
Keywords: crash
I use builds downloaded from the Mozilla.org ftp site.
Symlinked the plugin? I don't think so. I just let Mozilla install the xpi file
normally.
Comment 3•23 years ago
|
||
This is a known bug with java 1.3.x. See
<http://sources.redhat.com/ml/libc-alpha/2002-04/msg00143.html> (including the
followups, linked from the bottom of the page). Solution seems to be to use a
newer version of java.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Ok then. Thanks for the explanation.
Is a newer linux jre xpi going to be available soon?
I expect that I can just get a stock JRE from Sun's site and install the plugin
manually, but the xpi is convenient.
*** Bug 177149 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•