<?xml version="1.0" encoding='utf-8'?>
<!-- 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153
-->
<?xml-stylesheet type="text/xsl" href="https://mbien.dev/roller-ui/styles/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom">
    <title type="html">Michael Bien&apos;s Weblog</title>
    <subtitle type="html">don&apos;t panic</subtitle>
    <id>https://mbien.dev/blog/feed/entries/atom</id>
        <link rel="self" type="application/atom+xml" href="https://mbien.dev/blog/feed/entries/atom?tags=ubuntu" />
    <link rel="alternate" type="text/html" href="https://mbien.dev/blog/" />
    <updated>2024-08-24T07:57:58+00:00</updated>
    <generator uri="http://roller.apache.org" version="6.1.4">Apache Roller</generator>
    <entry>
        <id>https://mbien.dev/blog/entry/enabling_the_new_java_browser</id>
        <title type="html">Enabling the new java browser plugin on ubuntu</title>
        <author><name>mbien</name></author>
        <link rel="alternate" type="text/html" href="https://mbien.dev/blog/entry/enabling_the_new_java_browser"/>
        <published>2009-05-17T01:36:52+00:00</published>
        <updated>2019-04-07T09:21:14+00:00</updated> 
        <category term="Java" label="Java" />
        <category term="java" scheme="http://roller.apache.org/ns/tags/" />
        <category term="ubuntu" scheme="http://roller.apache.org/ns/tags/" />
        <content type="html">&lt;p&gt;When you are using Ubuntu and upgraded from older releases to
intrepid or jaunty you might have run into a setup bug which causes the
browser to keep using the old java plugin despite having latest Java SE
and plugin packages installed (e.g 1.6 update 13 from multiverse
repository).&lt;/p&gt;&lt;p&gt;To fix this you will have to update some symlinks and let them point to the correct location.&lt;/p&gt;&lt;p&gt;one easy way of doing this is by using the update-alternatives command:&lt;/p&gt;&lt;pre&gt; sudo update-alternatives --all&lt;br /&gt;&lt;/pre&gt;&lt;p&gt;this
will iterate through all symlinks in /etc/alternatives which have more than
one alternative and ask you which one to use. Simple update all links
which point to: &lt;/p&gt;&lt;pre&gt;.../libjavaplugin_oji.so&lt;br /&gt;&lt;/pre&gt;&lt;p&gt;to the location of the new plugin (e.g for i386):&lt;br /&gt;
&lt;/p&gt;&lt;pre&gt;/usr/lib/jvm/java-6-sun/jre/lib/i386/libnpjp2.so&lt;br /&gt;&lt;/pre&gt;&lt;p&gt;For all other links just hit Return. &lt;br /&gt;&lt;/p&gt;&lt;p&gt;This is a little bit of a brute force approach but there shouldn&apos;t be many of them and it is the only way to make sure you don&apos;t overlook one of them since they are all called differently ;) &lt;br /&gt;
&lt;/p&gt;&lt;p&gt;Next time you restart your browser the new plugin should be loaded
and applets which use e.g &lt;a href=&quot;//mbien.dev/blog/entry/java_javascript_interoperability_example&quot;&gt;jnlp for deployment&lt;/a&gt; (or out of process functionality) should work.&lt;br /&gt;
&lt;/p&gt;</content>
    </entry>
</feed>

