[CentOS] Java plugin (icedtea-web) does not load

[Toralf Lund]

On 19/08/14 14:57, Liam O'Toole wrote:
> On 2014-08-18, Toralf Lund <toralf.lund at pgs.com> wrote:
>> On 17/08/14 20:04, Liam O'Toole wrote:
>>> On 2014-08-17, Toralf Lund <Toralf.Lund at pgs.com> wrote:
>>>> Hi,
>>>>
>>>> After some recent upgrade or the other, the browser plugin for java no longer works in my CentOS 6 x86_64 setup - using Firefox. Applets won't load, and no java plugin is mentioned in "about:plugins". The "openjdk" Java packages as well as icetea-web are installed, though, and everything worked just fine a few weeks ago.
>>>>
>>>> Has anyone else seen this? Any idea what may be wrong and/or how to diagnose the problem? Should I expect error messages anywhere if the plugin just won't load (can't see anything in the browser console)?
>>>>
>>>> Note that when I talk about upgrades, I mean that I generally install all "notified" system updates.
>>>>
>>>> - Toralf
>>>>
>>> Does the file /usr/lib64/mozilla/plugins/libjavaplugin.so exist, and does
>>> it link (indirectly) to /usr/lib64/IcedTeaPlugin.so? You can check using
>>> the following command:
>>>
>>> 	readlink -e /usr/lib64/mozilla/plugins/libjavaplugin.so
>> I forgot to tell, I checked all "obvious" things like that. And yes, the
>> file points where it should.
>>
>> - Toralf
>>
> All I can think of is to run 'rpm -V' on the packages which own the
> above files, and also look for clues in ~/.xsession-errors and
> /var/log/messages upon starting firefox. I'm sure if those suggestions
> are obvious. :-)
Well, I guess the "obvious" was mainly verifying that the file was 
actually there :-)

The log files you mention didn't offer a clue about what was going on, 
but another file did - pluginreg.dat in the profile directory. It 
actually had

[INVALID]
/usr/lib64/IcedTeaPlugin.so:$
1385126043000:$

I then remove the file and restarted, and now everything is back on 
track :-)

I now remember doing this for other plugins in the past, but I'd quite 
forgotten that there even was such a file until I was reminded by a web 
search...

Another question is why the plugin was considered "invalid" in the first 
place, of course. Maybe I'll never find out...

- Toralf


>
> --
>
> Liam
>
>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos


This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.