Plug-In Installation - Access Denied
 

I need to install the X-Java-VM. I went to netscape, and started the automatic download and installation process for that plug in. As soon as it finished downloading, and begins the automatic installation process, it then stops and returns with a message "Access Denied".

So what do I do to override that, or how do I allow this java installation process access?

Mozilla
 

Oops, forgot to mention I'm using Mozilla....

youll have to run mozilla as root.

Under a terminal enter 'su' enter your root password, then type 'mozilla' to run your browser. Finally re-download the plugin and it will install it for you properly.

yep, i logged in as root, opened mozilla, tried it again and it worked. thanks

Hi,

and what if it installation's successfull but applets still won't appear?
I'm using Mozilla 1.5b and dowloaded and installed the proposed plugin from netscape (somewhat 6.2.2) but it wouldn't work.

The plugin doesn't appear in about:plugins either :o(

Can you guys help?

Thanks,

Philipp

if you read the readme from mozilla.org, you know that you should install java 1.4.2 (fukking unstable in my pc even if I already disable the caching function).

goto the plugin dir and
ln -s /usr/java/j2re1.4.2_01/plugin/i386/ns610-gcc32/libjavaplugin_oji.so

Still cannot get java working
 

I have tried logging in as root and running mozilla to get a auto download/install to run. This takes place and it says that it has had a sucessful installation, but java doesn't work on my page. I then tried downloading from sun's site, installed it, and set the link from the libjavaplugin.so to the plugins directory in mozilla. Still nothing!

I am running slackware 9 with mozilla 1.3 and mozilla firebird..:Pengy: Last time I was running slackware on this laptop it worked in like 20 seconds now i can't get this working at all.

I been having a similar problem, running redhat 9 and mozilla 1.2.1.

I logged on as root, went to netscape's plugin page & installed the java vm plugin. It said the installation was successful.

But I find that java applets are working only while I am logged onto my machine as root. If I log on as an ordinary user, it looks as if the plugin is not installed. When I let Netscape's page check for installed plugins, it shows nothing installed if I'm not root, but if I run the same check as root, it shows the java plugin is installed.

Is this a file permissions problem? Which file?

Hi, i had exactly the same problem. I don't understad why yet, but this simple solution seems to work for me,

1) download and run somewhere the Sun's Java RE 1.4.2 self extracting binary, from http://java.sun.com/j2se/1.4.2/download.html

2) as ordinary user do:
ln -s ./j2re1.4.2_02/plugin/i386/ns610/libjavaplugin_oji.so ~/.mozilla/plugins/

you will find more details in http://mozilla.weebeastie.net/java.shtml.
Good luck!

Evident (?) plugin permissions problem, j2sdk1.4.2
 

Same issue here; with Moz 1.2.1x and J2SDK 1.4.2, the java plugin inits for root
and no other. All users can run the jre console, demos, controlpanel, etc with no
evident errors.

Things that *don't* change the behavior:

- mods to mode and/or owner of files in the j2 tree
- moving between <mozilla>/plugins and ~/.mozilla/plugins configurations
- clearing and/or copying and/or duplicating the plugin db in ~/.mozilla/plugins
- removing and reinstalling all plugins but libnull
- modifying LD_PRELOAD (which was needed and worked for the earlier version)
- updating jre/beans/netbeans (at latest available, pre-release notwithstanding)
- updating mozilla (ditto above)
- rebooting (sorry, bad habit, was exposed to MS in an earlier life)
- removing and reinstalling mozilla, jre
- same as above with fresh accounts (non-priv'd) before reinstalling
- same as above with fresh accounts (non-priv'd) after reinstalling
- same as above on a fresh box (RH8@bundle and same@2.4.20-24.8smp)

Re: plugin install and permissions
 

When in doubt, punt ...

Solved the issue (ok, I actually traded it in for new issues) by going to Moz 1.5
and JRE 1.4.2. I've found a few other references to this problem and the common
factor was a combination of backrevs of *both* mozilla and jre.