Bug 59292 - Mozilla downloads wrong JRE plug-in
Summary: Mozilla downloads wrong JRE plug-in
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: mozilla
Version: 7.1
Hardware: alpha
OS: Linux
Target Milestone: ---
Assignee: Christopher Blizzard
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2002-02-04 19:10 UTC by Robert M. Riches Jr.
Modified: 2007-04-18 16:39 UTC (History)
0 users

Clone Of:
Last Closed: 2002-05-16 18:36:29 UTC

Attachments (Terms of Use)

Description Robert M. Riches Jr. 2002-02-04 19:10:47 UTC
Description of Problem: Mozilla downloads the wrong JRE
when it encounters a web page that needs a version 1.3.1
Java 2 plug-in.

Version-Release number of selected component (if applicable):

How Reproducible:

Steps to Reproduce:
1. Invoke mozilla
2. Go to page that requires a JRE 1.3.1 Java2 plug-in.
3. Make and check a hard link (cd /tmp; ln jre131i.xpi something;
    sleep 3600; unzip -t something)

Actual Results:
Mozilla downloaded an i386 JRE, which is not correct for an Alpha
machine.  (X86 may be the worst surviving instruction set architecture
on this planet, but it's certainly not the only one.)  Then, mozilla
pops up a window instructing the user to downloads a Losedows version
of the plug-in:
for Windows

Expected Results:
Mozilla should download a JRE appropriate for the architecture on
which it is actually running.  Or, better yet, if possible, it should
use the existing JDK already installed on the machine.

Additional Information:
I apologize for not being able to provide an URL that shows the
problem.  One case I saw was money.net's free 14-day trial for their
streaming real-time stock quote service.  Another is the charts page
on my stock broker's web site, and an account with the broker is
required to get to that area.  (It appears a fairly reliable predictor
of a page that will show this problem for Mozilla is a page that will
cause Netscape 4.77 to throw a segment fault.)

Comment 1 Christopher Blizzard 2002-04-29 17:35:10 UTC
So what would be the right behaviour here?  I don't think that we have a working
JVM for mozilla for the alpha, right?  Should I just disable the dialog?

Comment 2 Robert M. Riches Jr. 2002-04-29 17:50:59 UTC
That would be better than the present behavior.  If Mozilla requires a whole
separate JVM,
separate from a JDK the user might have already have on the machine, and if
there is no
downloadable JVM for the architecture in question, then it would be better to
inform the
user that no JVM exists for that machine.


Comment 3 john.goshdigian 2002-04-30 18:42:27 UTC
JVM exists for Alpha, the problem is with the plug-in.
So, it would be better to inform the user that no plug-in exists for that machine.

Comment 4 Christopher Blizzard 2002-04-30 19:51:19 UTC
Where is the JVM?

Comment 5 Christopher Blizzard 2002-05-16 18:36:24 UTC
I fixed this in the 0.9.9 build by not allowing the plugin downloader to go to
the downloader site.  Downloading and installing a .xpi as a user doesn't work
correctly in any case.

Comment 6 Christopher Blizzard 2002-05-16 18:37:08 UTC
Anyway, fixed in the last 7.2 errata.

Note You need to log in before you can comment on or make changes to this bug.