I am running Virtualmin/Webmin 3.70 on Ubuntu 8.04 installed from install.sh. My client machine from which I access Webmin is running Ubuntu 9.04 64 bit version. When I try to access File Manager, my browser (Firefox 3.0.11) simply disappears. Could anyone give suggestions on how to start trouble-shooting this problem.
My problem is that while I am used to debugging Java in IDE environments, I have no idea how one debugs an applet in a browser. I think that the problem occurs when the browser attempts to launch the applet and may also be associated with the fact that the JVM is 64 bit as well as the operating system (Sun JDK 1.6.13). Looks like I need to do some research.
for long there wasn’t a 64 bit applet. Sun hadn’t written it. And one would install the 32bit firefox along side of the 64bit firefox. But times have finally changed.
I think you need libnpjp.so (it’s called, The Java™ Plug-in, Java SE 6).
it is likely the java install on your desktop. I had some trouble in the beginning as well untill I installed a different java version. sun-java6-jre and sun-java6-bin and sun-java6-plugin is what I have next to java-common.
I had a similar problem with Jaunty, Java, and Firefox.
Thanks, Ronald, because one of the issues may have been that I had missed the -plugin package you reference above.
Several hours later, I remember that the instructions that I found most helpful for installing the latest Java version (not Sun’s, which are not bad) mentioned that you might have to remove IcedTea.
I recall that some other update process had installed that earlier, and had noted the interesting name. Good thing to watch what Synaptic does, I am finding.
I thought that I had removed it, but it was still in Synaptic, so I removed it, restarted FF, and voila! Java.
I also found this which you might find interesting: how to switch between Java versions-
Follow the instructions in the above link and Run the applet again, deselect the “Always trust” checkbox, and click the “Sandbox” button. The applet should then run normally. If it does not, please open a new bug report and attack the stack trace from that failure.