Closed
Bug 255501
Opened 21 years ago
Closed 21 years ago
Firefox crashes when opening about:plugins with Java plugin enabled
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: krzysiek.pawlik, Assigned: bugzilla)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040809 Firefox/0.9.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040809 Firefox/0.9.3
When Java Plugin (Blackdown JRE 1.4.1) is enabled (symlink points to
javaplugin_oji.so) opening any website that uses java crashes firefox with
following message:
INTERNAL ERROR on Browser End: Could not get the JVM manager
System error?:: Success
Opening about:plugins crashes the browser also.
Reproducible: Always
Steps to Reproduce:
1. ln -s /opt/blackdown-jre-1.4.1/plugin/i386/mozilla/javaplugin_oji.so
/usr/lib/MozillaFirefox/plugins/
2. start firefox
3. open 'about:plugins'
Actual Results:
Crash
Expected Results:
Open page with information about plugins
| Reporter | ||
Comment 1•21 years ago
|
||
This is not a bug in Firefox.
Adding 'java' to USE flags resolved this.
(distro: Gentoo)
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Comment 2•21 years ago
|
||
Hm... did you emerge mozilla-firefox or mozilla-firefox-bin?
The reason I ask is because I don't have Java in my use flags, but it still
works. I use Blackdown-1.4.1-01.
| Reporter | ||
Comment 3•21 years ago
|
||
emergeed mozilla-firefox - compiled it from scratch. prior to 0.9.3 everything
worked ok without the 'java' flag.
(In reply to comment #3)
> emergeed mozilla-firefox - compiled it from scratch. prior to 0.9.3 everything
> worked ok without the 'java' flag.
I have the java flag and it still doesn't work. I've tried it in Mozilla,
Firefox, and Galeon, always does the same thing. I've tried blackdown, ibm, and
sun JVMs
| Reporter | ||
Comment 5•21 years ago
|
||
(In reply to comment #4)
> I have the java flag and it still doesn't work. I've tried it in Mozilla,
> Firefox, and Galeon, always does the same thing. I've tried blackdown, ibm, and
> sun JVMs
Hm.. I can't really say what is causing it. (before re-emerge of firefox, I've
also tried blackdown, ibm and sun JVM (in that order) - every one of them caused
the browser to quit with this message)
Maybe this one should be reopened?
| Reporter | ||
Comment 6•21 years ago
|
||
Got it!
from /usr/portage/eclass/mozilla.ecalss:
----------
myconf="${myconf} $(mozilla_use_enable java oji)"
----------
so portage disables OJI when built without "java" in USE, and this somehow
trashes FF when it attempts to show "about:plugins" with Java plugin symlink in
plugins/ directory.
(In reply to comment #6)
> Got it!
> from /usr/portage/eclass/mozilla.ecalss:
>
> ----------
> myconf="${myconf} $(mozilla_use_enable java oji)"
> ----------
>
> so portage disables OJI when built without "java" in USE, and this somehow
> trashes FF when it attempts to show "about:plugins" with Java plugin symlink in
> plugins/ directory.
>
So should there be a USE="oji" in there as well?? Or is that even a USE flag?
Because I have double checked and recompiled, and I certainly have java enabled,
but it still wont work
| Reporter | ||
Comment 8•21 years ago
|
||
(In reply to comment #7)
> So should there be a USE="oji" in there as well?? Or is that even a USE flag?
oji is not a USE flag - adding "java" should be sufficent
Well, again I say, I had java set and it didn't work. But I threw in oji and it
didn't get in the way, because now it worked. Perhaps it was just the order I
installed things in, but it works.
You need to log in
before you can comment on or make changes to this bug.
Description
•