chromium-browser: No Java Pepper Plugin available

Bug #1308783 reported by ramgorur
338
This bug affects 75 people
Affects Status Importance Assigned to Milestone
Chromium Browser
Unknown
Unknown
Iced Tea
Won't Fix
High
chromium-browser (Ubuntu)
Undecided
Unassigned

Bug Description

I was using google chrome browser on Ubuntu 12.04 machine, recently I needed to switch to chromium-browser. I am using the version that is available on the Ubuntu software centre. The problem is that I can't make java applets to load any more.

Here is my situation --

 1. I am using vanilla jdk (jdk 1.7.0_51) from the oracle site.
 2. Previously in chrome, I have created a symlink of `libnpjp2.so` to the `/opt/google/chrome/plugins` folder, java applets were working fine.
 3. After uninstalling chrome and installing chromium-browser, I made a symlink of `libnpjp2.so` to `/usr/lib/chromium-browser/plugins` folder, but java applets do not fire up any more (even from this site: http://www.java.com/en/download/installed.jsp)
 4. Even `libnpjp2.so` appears in `about:plugins` in chromium-browser and showing it's enabled.

What I have tried so far --

 1. After uninstalling chrome, the `/opt/google/chrome` was still there, I removed it
 2. Made the symlink as the point 3 above to `/usr/lib/chromium-browser/plugins`, but no luck.
 3. So, I installed `icedtea-7-plugins` from the Ubuntu repo and made a symlink of `IcedTeaPlugin.so` to `/usr/lib/chromium-browser/plugins`, but no luck, so I removed it.
 4. Even added the java applet test page to the exclusion list in the java control panel.
 5. Even cleared temporary internet files from the java control panel.
 6. Did multiple cycles of "enable/disable" java plugins in chromium-browser.
 7. Firing up the chromium-browser with `-enable-plugins` switch did not work.

When I go to the java applet test page, what I can only see is a grey rectangle, nothing else. Please note, everything was working fine on chrome browser and also in firefox. Please also note that I do not want to install openjdk stuffs.

any idea ?

lsb_release -rd:

Description: Ubuntu 12.04.4 LTS
Release: 12.04

chromium-browser:
  Installed: 33.0.1750.152-0ubuntu0.12.04.1~pkg879.1
  Candidate: 33.0.1750.152-0ubuntu0.12.04.1~pkg879.1
  Version table:
 *** 33.0.1750.152-0ubuntu0.12.04.1~pkg879.1 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/universe amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ precise-security/universe amd64 Packages
        100 /var/lib/dpkg/status
     18.0.1025.151~r130497-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages

ramgorur (code-icted)
summary: - java plugin does not work on chromium
+ chromium-browser: java plugin does not work
tags: added: aura
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: chromium-browser: java plugin does not work

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
Revision history for this message
Fabio Marzocca (thesaltydog) wrote :

Doesn't work on 14.04 either.

Revision history for this message
udippel (udippel) wrote :

It explicitly does not work on 14.04 after the update from 13.10.

Do we have a tag 'regression'?
The worst part is, that Dr. Google always starts by returning a dozen websites stating that:
sudo apt-get install icedtea-7-plugin openjdk-7-jre
would do it. No idea from whence they get this??

Revision history for this message
Jostein (josteinaj) wrote :

It doesn't work for me anymore either. I think it stopped working when I upgraded to 14.04.

Revision history for this message
Anthony Fok (foka) wrote :

A good answer to this issue is provided here:

    http://askubuntu.com/questions/450683/java-plugin-in-chromium

Quote:

    Java (IcedTea) doesn't have a PPAPI plugin available,
    and so it's not usable in Chromium, since Chromium 34 in Trusty
    has switched to the Aura rendering framework
    and no longer allows NPAPI plugins.
    See also https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1308783.

Glossary:

    NPAPI: Netscape Plugin Application Programming Interface,
                  "a cross-platform plugin architecture used by many web browsers.

    PPAPI: Pepper Plugin API,
                  "a set of modifications to NPAPI to make plugins more portable and more secure"

Revision history for this message
In , David Lenz (dtl135dtl135) wrote :

Google Chrome 35 has dropped support for NPAPI plugins (so icedtea no longer works there). Is there a plan to make a PPAPI-compatible version of icedtea?

information type: Public → Public Security
information type: Public Security → Public
Revision history for this message
Titantux (israel-m-dj) wrote :

Just to let you know than, had to rollback to Chrome 33.0.1750.152-1 in order to get working again java besides others plugins again on Ubuntu 14.04.

If you have and urgent case here is the link where you are able to download previous versions:

http://mirror.pcbeta.com/google/chrome/deb/pool/main/g/google-chrome-stable/

Regards,
Titantux

Revision history for this message
In , Javier Domingo (txomon) wrote :

I have tracked down to this bug, which seems to be the source of java applets not working on chromium.

Is any update on this bug?

Revision history for this message
In , Aazores (aazores) wrote :

Yes, this is indeed the cause for Java applets no longer working in Chrome/Chromium - Google has removed the plugin API which IcedTea-Web uses. We haven't yet determined if it is even possible to create a port of IcedTea-Web to PPAPI, due to the sandboxing and other restrictions Google places on extensions built with Pepper/Native Client.

Revision history for this message
In , Mattias-eliasson (mattias-eliasson) wrote :

There are a relevant discussion about this here: http://www.firebreath.org/display/documentation/Browser+Plugins+in+a+post-NPAPI+world

The short answer are that there are no sufficient replacement for NPAPI in Chrome. Chromium are open source so it could potentially be modified.

Currently my brightest idea are to use DLL injection and override the entire engine component with something similar to Chrome Frame. If we simply run another browser engine, such as a modified Chromium engine with NPAPI-support, that might work. Or an engine that do not require any hacking such as Qt WebKit which supports NPAPI plugins out of the box.

Another option would be to make a completely Chrome-compatible browser out of Chromium, which are what the Qt WebEngine are all about. Such a browser could be entirely FOSS and shipped with Linux distributions. A mayor problem would be the Flash plugin which may require that Chrome are also installed. As a system admin I would like to avoid installing Chrome in such a scenario, or at least hide it well.

Revision history for this message
In , helpcrypto (helpcrypto) wrote :

Altough a bug report is not the best place to chat, I'll give you my 2 cents:

 - Assume you arent going to use Chrome for a while. Firefox, Safari and IE will work.
 - If possible, use JNLP. AFAIK it will continue working.
 - If you, like me, are using applets for electronic signature, probably the best option is to keep praying for Webcrypto+FIDO

Regards.

Revision history for this message
Redsandro (redsandro) wrote :

IcedTea is an NPAPI plugin and is no longer supported by the latest Chromium builds.
The Java library is called `libnpjp2.so`, and I am /guessing/ that "libnp" means this is also NPAPI.

https://en.wikipedia.org/wiki/NPAPI#Browser_support

_Google Chrome / Chromium: In September 2013, Google announced that NPAPI support in Chrome would be phased out during 2014 because "NPAPI’s 90s-era architecture has become a leading cause of hangs, crashes, security incidents, and code complexity."_

Revision history for this message
Varun Mittal (viral.mutant) wrote :

What is the work around for getting it working on 14.04 ?

Revision history for this message
Vincent Gerris (vgerris) wrote :

There is no work around for version 35.
You can revert to an earlier version, use Firefox or develop a PPAPI based plugin is developed.
I hope this bug report is the base for a solution.

Revision history for this message
Peter (zyzynka) wrote :

Happened to me when I switched to qiana (from petra). Titantux's link to version 33 is the solution until PPAPI plugin comes to existence.

Revision history for this message
David Dombrowsky (davek) wrote :

Sounds like a rather suspicious move on Google's part, to break support for the open source API and force people to use Oracle's closed-source JAVA solution. Do not like. Chrome just went way down in my book.

Revision history for this message
Fredrik Wendt (fredrik-wendt) wrote :
summary: - chromium-browser: java plugin does not work
+ chromium-browser: No Java Pepper Plugin available
Chad Miller (cmiller)
Changed in chromium-browser (Ubuntu):
status: Confirmed → Won't Fix
Changed in icedtea:
importance: Unknown → High
status: Unknown → Confirmed
Revision history for this message
In , Alberto Salvia Novella (es20490446e) wrote :
Revision history for this message
In , Alberto Salvia Novella (es20490446e) wrote :

Plug-ings will be dropped from both Chromium and Firefox, so fixing this bug won't have any impact in medium term.

Revision history for this message
In , Jvanek (jvanek) wrote :

ITW provides little fall back in form of "javaws -html some.html.page.url"
But yes, it have to much cases when it is useless.

Long story short, there is no plan for PPAPI.

If you wont one. Please contribute!

Revision history for this message
In , David Lenz (dtl135dtl135) wrote :

Fair enough. Thanks.

Changed in icedtea:
status: Confirmed → Won't Fix
Revision history for this message
David Thomson (kp-ubuntu1-5k) wrote :

I am not an expert, but somehow I got Java working in Chromium on one of my Ubuntu computers. All my software is updated to current versions. If someone wants to guide me through a process of discovery, I can find out how I got it to work. I would like to know what I did, as I need to install Java on newer machines.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.