Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Starred by 83 users
Status: WontFix
Owner: ----
Closed: Apr 2014
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug

  • Only users with EditIssue permission may comment.

Sign in to add a comment
IcedTea Java Plugin not recognized with 35.0.1916.27 beta aura
Reported by, Apr 14 2014 Back to list
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.27 Safari/537.36

Steps to reproduce the problem:
1. Visit about://plugins

What is the expected behavior?
The IcedTea Java Plugin should be listed like below.  That's the plugin description from chrome 34.0.1847.116 where it works fine.

IcedTea-Web Plugin (using IcedTea-Web 1.5) - Version: 1.5)
The IcedTea-Web Plugin executes Java applets.
Name:	IcedTea-Web Plugin (using IcedTea-Web 1.5)
Description:	The IcedTea-Web Plugin executes Java applets.
Version:	1.5)
Location:	/usr/lib/jvm/java-7-openjdk/lib/
MIME types:	
MIME type	Description	File extensions
application/x-java-vm	IcedTea	
.class	.jar
application/x-java-applet	IcedTea	
.class	.jar
application/x-java-applet;version=1.1	IcedTea	
.class	.jar
application/x-java-applet;version=1.1.1	IcedTea	
.class	.jar
application/x-java-applet;version=1.1.2	IcedTea	
.class	.jar
application/x-java-applet;version=1.1.3	IcedTea	
.class	.jar
application/x-java-applet;version=1.2	IcedTea	
.class	.jar
application/x-java-applet;version=1.2.1	IcedTea	
.class	.jar
application/x-java-applet;version=1.2.2	IcedTea	
.class	.jar
application/x-java-applet;version=1.3	IcedTea	
.class	.jar
application/x-java-applet;version=1.3.1	IcedTea	
.class	.jar
application/x-java-applet;version=1.4	IcedTea	
.class	.jar
application/x-java-applet;version=1.4.1	IcedTea	
.class	.jar
application/x-java-applet;version=1.4.2	IcedTea	
.class	.jar
application/x-java-applet;version=1.5	IcedTea	
.class	.jar
application/x-java-applet;version=1.6	IcedTea	
.class	.jar
application/x-java-applet;version=1.7	IcedTea	
.class	.jar
application/x-java-applet;jpi-version=1.7.0_50	IcedTea	
.class	.jar
application/x-java-bean	IcedTea	
.class	.jar
application/x-java-bean;version=1.1	IcedTea	
.class	.jar
application/x-java-bean;version=1.1.1	IcedTea	
.class	.jar
application/x-java-bean;version=1.1.2	IcedTea	
.class	.jar
application/x-java-bean;version=1.1.3	IcedTea	
.class	.jar
application/x-java-bean;version=1.2	IcedTea	
.class	.jar
application/x-java-bean;version=1.2.1	IcedTea	
.class	.jar
application/x-java-bean;version=1.2.2	IcedTea	
.class	.jar
application/x-java-bean;version=1.3	IcedTea	
.class	.jar
application/x-java-bean;version=1.3.1	IcedTea	
.class	.jar
application/x-java-bean;version=1.4	IcedTea	
.class	.jar
application/x-java-bean;version=1.4.1	IcedTea	
.class	.jar
application/x-java-bean;version=1.4.2	IcedTea	
.class	.jar
application/x-java-bean;version=1.5	IcedTea	
.class	.jar
application/x-java-bean;version=1.6	IcedTea	
.class	.jar
application/x-java-bean;version=1.7	IcedTea	
.class	.jar
application/x-java-bean;jpi-version=1.7.0_50	IcedTea	
.class	.jar
application/x-java-vm-npruntime	IcedTea	

What went wrong?
The IcedTea Java Plugin is not shown at all with 35.x.  Browsing a site requiring Java will show the missing plugin bar on top.

I've installed chrome 34.0.1847.116 (stable) and 35.0.1916.27 (beta) side-by side on my system.  The former recognizes the plugin flawlessly, the latter doesn't.

Did this work before? Yes 34.0.1847.116

Chrome version: 35.0.1916.27  Channel: beta
OS Version: 
Flash Version: Shockwave Flash 13.0 r0

Labels: Cr-Internals-Plugins
Status: WontFix
Aura Linux doesn't support NPAPI plugins.
 Issue 376149  has been merged into this issue.
 Issue 375909  has been merged into this issue.
 Issue 376149  has been merged into this issue.
 Issue 375909  has been merged into this issue.
 Issue 377296  has been merged into this issue.
I will use Firefox as my default browser. I need the java plugin to connect to my home banking site.
Comment 9 by, May 26 2014
Very clever move, congrats. Java applets are nowhere to be found nowadays anyway, it is only required to manage some silly hardware made by dying vendors like IBM, HP, EMC and alike. Oh, and banks of course, but who needs online access to bank?

Thanks God there is Firefox.
Comment 10 by, May 26 2014
@jetc: while I don't approve of the Chrome change, the reality is that if a bank requires Java for the web and has no mobile presence, then folks really should think about switching banks. 
@snap: Well, switching banks may work for you, but in Denmark, the whole national infrastructure, i.e tax reporting, health care, school enrollment, etc is based on a single national login-system:
And guess what, it uses Java.
This has been criticized as a security issue, but the government is not listening.
@stuartmorgan: What about Fedora Linux?
Unfortunately, no java, no chrome.
Firefox is coming back with full strength.
What a shame with linux users!
This now means that hundreds of thousands of IPMI/iDrac capable server systems can no longer be managed using chrome.
I used to use Chrome to access our SSL vpn which uses a java front end to setup the vpn tunnel behind the scenes.  Disappointing that they just decided to yank this without any kind of workaround past downgrading.  Seems like a pretty poor decision.
Looks like I need to switch back to iceweasel/firefox :-( Too bad that Google is kicking out a technology like java, which is widely used in business/professional environment.
WontFix -> will quit chromium, maybe google at all!
It would be very cool if someone forked Chromium at version 34 and released a new open source browser target to Linux, where developers really had care about Linux users, and didn't do stupid things like this.

Labels: Restrict-AddIssueComment-EditIssue
The comments here are mostly not productive, so I'm locking this bug. If you want to provide general feedback, please use the product forums.
 Issue 375909  has been merged into this issue.
 Issue 382323  has been merged into this issue.
Comment 22 by, Jul 25 2014
 Issue 392984  has been merged into this issue.
 Issue 424902  has been merged into this issue.
It appears this bug never ended up with a link to the thread explaining the decision, just some of the duplicates. Sorry for that oversight.

For anyone looking for background on this decision, the announcement and reasoning are here:!topic/chromium-dev/xEbgvWE7wMk
 Issue 470923  has been merged into this issue.
Sign in to add a comment