Frmservlet.jnlp file. Select Open with Java™ Web Launcher and select Do this automatically for files like this from now on. When these options are selected, Firefox will automatically open the Java Web Launcher on subsequent logins. Note: If you inadvertently chosen 'Save As' and save the JNLP file to the desktop, then you will.
- In Firefox version 66.0.4 when I download a.jnlp-file it provides the option to either save the file or open it in Java Web Start. Now that I updated to Firefox version 67.0 I can only save the file. The option to directly open the file using Java Web Start is not available anymore.
- Because you run it from IE C: Users obzbuxc AppData Local Microsoft Windows INetCache IE BNTD9VNR AccessibleScrollDemo.jnlp and IcedteaWeb don't know the IE proxy settings (only Firefox) — You are receiving this because you authored the thread.
Have you followed the instructions I linked to? Have you run firefox from a terminal and tried to run a jnlp file so you could observe any error output?
These are rhetorical questions. It would seem you haven't. Please do so.
I followed the links instructiuon on creating a symlink and placed it in my local .mozilla but firefox already sence the icedTea-web since I can choose it when trying to launch a .jnlp.
No .jnlp file can be launched thru firefox but when saving a .jnlp file local and running from terminal I can get test .jnlp to run but when running the one I want to launch, a iKVM for my server, it just says 'Download ATEN java iKVM viewer: 0%' (and blinking!?) This I am wondering if it actually could have something to do with I am running 64 bit java or if it is not possible to run a iKVM for a server locally and it has to be launched from website when I am logged in to SuperMicro, I have no idea on this part.
NOW after just waiting a few minutes the downloading started and then It ask me if I trusted SuperMicro and then I pressed 'Run' but then it hangs and gives me these 'Details':
And if I press the tab 'java console':
https://pastebin.com/nM8JvLtC
Firefox 52 began its roll out yesterday, bringing a bunch of small iterative improvements to the fore.
Among the most significant change in the release is the decision to disable support for all NPAPI plugins bar Adobe Flash by default.
This is a good move in the round as NPAPI is a terribly outdated technology (over 20 years old, in fact). Whatever bonuses these plugins, Flash, Silverlight and Java among them, offered have been long since outweighed by the inherent security flaws manipulated to malicious ends.
Google Chrome ditched NPAPI support back in 2014 (and the version of Flash that ships pre-bundled uses the newer PPAPI tech).
But it is in Firefox 52, with Mozilla’s first step towards total removal of the technology from its browser, that is likely to impact Linux users the most.
Renable NPAPI Plugin Support in Firefox 52
If there’s a particular NPAPI plugin that you rely on there is (for now) a way to override Firefox defaults and re-enable NPAPI support.
Reader Grof has all the details.
“This is important, because some websites are still using Java plug-ins, like for example our government site for signing documents. You can’t work with government if no Java plugin is present,” he explains.
“But there is a way to enable Java, Silverlight etc NPAPI plugins in Firefox 52 using an about:config setting. Add new Boolean string 'plugin.load_flash_only' and set it to false. Then restart the browser.”
That’s it; assuming your NPAPI plugins are installed correctly they should work as before.
It’s a Short Term Solution
Firefox Jnlp File
In Firefox 53, Mozilla will remove this workaround. Consider this a short-term, stop gap solution. If you think you’ll need a little longer to transition away from such plugins you should download Firefox ESR (Extended Support Release), where NPAPI plugins will continue to work for another year.