Description of problem:
When visiting pages that require a special plugin, such as Flash or
Java, you get a "this page require a plugin to be viewed correctly.
Click here to install it". If i click the button, i get a (really
nice) dialog which finds the correct plugin (in the case of flash, not
in the case of java), and downloads it. But when it is finished
downloading, it just gives a sour message about the instalation failing...
Version-Release number of selected component (if applicable):
1.0
How reproducible:
haven't tried
Steps to Reproduce:
1. go to "www.nrk.no"
2. se the nice litte firefox banner
3. click the install plugins button
4. next, next, next...
5. fails
Actual results:
no installation of plugin
Expected results:
plugin should be installed in user's home directory
Additional info:
This worked when using the official installer

I have a similar problem, when trying to install search plugins in the
search bar.
The dirty trick is to make the
/usr/lib/firefox-1.0/{searchplugins,plugins} directories writable by
the user you normally use to run firefox. this is dirty and not secure.
Earlier, Firefox/Mozilla used to ask the user wether she/he wanted to
install the extension/plugin/searchplugin system-wide or for his sole
profile. Where did this code go ?

The Flash install should work fine with FC4T3 now. The problem was originally
tracked on bug 152611, and then moved to bug 151870. You can read both for
details, but RPM was setting the wrong SELinux security context on the home
directory, so that the plugins would not run after they were installed. I just
verified that things are working great with Flash on FC4T3.
If someone wants to point me to a site that auto-installs Java, I'll give that a
shot as well.
-Sean

Hmm.. i know one, but you'll need a password and username
(https://www.its-learning.com)
I don't think java install works on upstream either (at least not in Linux) - i
think it complained "could not find plugin" or something like that.
Could SE-linux also be the problem with translations?

Alright-
I just visited a webpage that required JAVA, and firefox correctly routed me to
Sun's page to install Java. It also informed me that it could not be installed
automatically, and would have to be manually installed. (As a separate issue,
the Java RPM from Sun does not work after installation). This is not a bug
with Firefox, however, which works correctly with both Flash (auto-install)
works fine, and Java (points to an RPM as it can not auto-install it). I would
say that this bug can be closed as "Not A Bug" or "Rawhide" (as the Flash issue
did exist at one time, but works now in Rawhide). Once I figure out what is
causing the Java install to not work via RPM, I will file a bug with the
appropriate component.
-Sean

FC4 users are advised to not use Sun's Java RPM. It contains Provides that
conflict with names used in FC4's packages, meaning Sun Java might disappear
from an installed system during package upgrade operations. FC4 users should use
either jpackage's RPM or install manually the Sun Java tarball into /opt. Sun
Java 1.5+ is recommended for stability purposes.

Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Thank you!

Closing per lack of response to previous request for information.
This bug was originally filed against a much earlier version of Fedora
Core, and significant changes have taken place since the last version
for which this bug is confirmed.
Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only. Please install a still supported version and retest. If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version. Otherwise, if this a security issue, please change the
product to Fedora Legacy. Thanks, and we are sorry that we did not
get to this bug earlier.

Note

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