Closed
Bug 99866
Opened 23 years ago
Closed 23 years ago
mozilla fails to detect Java plugin version under Red Hat Linux 7.1
Categories
(SeaMonkey :: Build Config, defect)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: ct7, Assigned: blizzard)
References
()
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010913 BuildID: 2001091323 Under RedHat Linux 7.1, the mozilla script fails to correctly detect the version of the Java plugin, causing the browser to hang because LD_ASSUME_KERNEL=2.2.5 isn't being set. Reproducible: Always Steps to Reproduce: 1. Install mozilla from RedHat 7.X RPMS 2. Install the Java plugin 3. $ sh -x mozilla http://java.sun.com/ Actual Results: The mozilla script fails to set LD_ASSUME_KERNEL=2.2.5 before starting mozilla-bin, which causes the Java plugin to fail. The problem is that the script fragment to detect the version of the Java plugin assumes that "cut" will be in the PATH; on RedHat Linux 7.1, cut is installed as /bin/cut, instead of /usr/bin/cut. Apparently /bin isn't in the search PATH, so the fragment fails because it can't find "cut". What's strange is that /bin is in the path right before the test, but it fails, but symlinking /usr/bin/cut -> /bin/cut clears up the problem.
*** This bug has been marked as a duplicate of 79918 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 4•23 years ago
|
||
This isn't resolved, since it isn't a duplicate. Someone put code into the mozilla script to detect the older Java plugin, all I was asking is that someone fix that code to correctly parse the Java version.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Assignee | ||
Comment 5•23 years ago
|
||
The cut path is hard coded into the java startup script. That's part of Java, not Mozilla. I can't fix that.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → INVALID
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•