Closed Bug 210622 Opened 22 years ago Closed 21 years ago

Release notes not detailed enough for using Sun Java Plugin on Red Hat 7.2

Categories

(Core Graveyard :: Java: OJI, defect)

Product:
Core Graveyard
Component:
Java: OJI
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: jim_nance, Assigned: yuanyi21)

References

(
URL
)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 I just installed mozilla 1.4 rc3 on a Red Hat 7.2 system. I also installed the Sun 1.4.2 JRE refered to by the link in the release notes, and made the plugin symlink as described in the release notes. When I start mozilla with the plugin link present, I get a message which indicates that the java plugin needs libgcc_s.so which is not present on a Red Hat 7.2 system. I solved this problem by copying the libgcc_s.so from a Red Hat 9 system into my mozilla installation directory. I believe the release notes should mention this. Reproducible: Always Steps to Reproduce: 1. 2. 3.
First I will check libgcc_s.so is used by java plugin or mozilla
Status: NEW → ASSIGNED
yes, the libgcc_s.so is used by java plugin, Xiaobin, should JPI release engineer build a libjavaplugin_oji.so that independent to libgcc_s.so? (static link?)
As I mentioned in another bug report, the intention of build GCC 3.2 version of Java Plugin is to support modern version of Linux such SuSE 8.1 or later, RedHat 8.0 or later. We don't have a plan to build a plugin statically link to libgcc_s.so.1. Unless there is a need for this, we won't do it.
*** Bug 208421 has been marked as a duplicate of this bug. ***
If you are going to deprecate bug 208421 as being a duplicate of this (higher-number) bug, please create a more generic tracking bug. In particular, the other bug affected people using JDK1.4.1xx whereas this one describes a beta version of JDK 1.4.2. Likewise, the previous bug affected all Linux (and I suspect BSD) distributions, whereas this one limits itself to an outdated version of RedHat... Thanks, Daniel
I'm workin' on it. http://mozilla.org/releases/mozilla1.4/README.html#new-issues and http://mozilla.org/releases/mozilla1.4/known-problems.html#java (updates may not show up for another hour or so.) I think mozilla.org will also be making available an egcs 1.1.2 build for those on older systems. Which plugin should those people use?
They should use the one in the ns610 directory: tricia> ls /usr/java/j2re1.4.2/plugin/i386/ ns4/ ns610/ ns610-gcc32/
*** Bug 211028 has been marked as a duplicate of this bug. ***
Note that you can fix older Red Hat versions by installing the GCC supplements for Red Hat 7.3 (GCC 3.1 Compiler Suite for Red Hat Linux 7.3). Most people don't have acces to a Red Hat 8 or 9 to copy their version of libgcc_s.so.
*** Bug 210583 has been marked as a duplicate of this bug. ***
This seems like a reasonable solution. Putting a note on http://www.mozilla.org/releases/mozilla1.4/installation-extras.html#extras_java would also help. Thanks for clearing up the confusion. Later, Daniel
Asa, in http://www.mozilla.org/releases/mozilla1.4/installation-extras.html#extras_java Would you please to add some notes following: "In Linux Put a symlink to /usr/java/jre<version>/plugin/i386/ns610/libjavaplugin_oji.so in your plugins/ directory. " For example: "If you are using mozilla that built by gcc 3.x, Put a symlink to /usr/java/jre<version>/plugin/i386/ns610-gcc32/libjavaplugin_oji.so in your plugins/ directory. (version >= 1.4.2" Thanks!
FYI, when I used the version of Mozilla built for gcc-2.96-112.7.2 and Red Hat 7.2 (fully patched): mozilla-i686-pc-linux-gnu-egcs112-1.4.tar.gz And downloaded and installed j2re-1.4.2-fcs (no longer beta) And pointed: /usr/local/mozilla/plugins/libjavaplugin_oji.so -> /usr/java/j2re1.4.2/plugin/i386/ns610/libjavaplugin_oji.so Mozilla 1.4 now works for me. Thanks for the build and for the instructions. You all may not be the right people to mention this too, but its worth saying... it took some doing to get this to work! Red Hat 7.2 is not that old. I hope the next build doesn't require a CS degree to get working on RH 7.2. On the bright side, Java no longer crashes my Mozilla browser when I leave a java page and go to a regular HTML page. Great!
I am also having problems. I am running Mozilla 1.4 on Redhat 8.0. I built Mozilla from the Source RPMs and it seems to be working fine. Except for java. I downloaded the JRE 1.4.2 from Sun and installed. I made the symlink, as directed, to the plug-in which then shows up in the Help-AboutPlugins. However, when I try to browse to a java-enabled page, I get "This page gets information of a type (applicaton/x-java-vm) that can only be viewed with the appropriate plug-in." Yet if I view my plug-ins with Help-About PlugIns that is the first mime-type listed as being installed. So what gives? There's no issue of permissions. One other thing, my symlink is to the ns610-gcc32 version of the plugin as indicated in the Mozilla documentation. I had also tried the plain ns610 version as is indicated in some other documentation. When the symlink pointed to that, Mozilla would try to load but die before coming onscreen.
For last comment: After the symlink is made, make sure you shut down the browser completely.
Thanks for the suggestion but it doesn't help. Although the plugin is shown as loaded, no java-enabled pages work and the Java Console refuses to come up. Are there any other ideas of what I can do? Why does one component see the plugin and other components don't? Is there a log someplace where I might find an error message?
set JAVA_PLUGIN_TRACE to 1 and run Mozilla in debug mode to see if any output gives out.
*** Bug 214659 has been marked as a duplicate of this bug. ***
->kyle
Assignee: joshua.xia → kyle.yuan
Status: ASSIGNED → NEW
This is not really relivant anymore. I am going to close this.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.