FULL PRODUCT VERSION :
java version " 1.7.0_25 "
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)


ADDITIONAL OS VERSION INFORMATION :
Linux caleb 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2+deb7u2 x86_64 GNU/Linux


EXTRA RELEVANT SYSTEM CONFIGURATION :
Google Chrome 28.0.1500.52

A DESCRIPTION OF THE PROBLEM :
libnpjp2.so does not report any version number on Linux. This means that Chrome always reports that it is out of date and should be updated - see https://code.google.com/p/chromium/issues/detail?id=137388

This bug is like #8010789 - reported on Solaris, but with a comment expressing doubt over the Version field. Let me clear that up: the version should be in the Version field, not embedded in the name field. Database 101: fields should be atomic.

The Mac folks agree, and in #8000368 agreed to put the version number in the Version field.



STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Install Chrome.
2. Install Java JRE and plugin (Chrome will find the plugin from ~/.mozilla/plugins/libnpjp2.so symlink or similar)
3. Go to http://www.java.com/en/download/testjava.jsp
4. Go to chrome://plugins/


EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
In step 3, the java applet should run (so long as the JRE is up-to-date)

In step 4, the entry for the java plugin should report the version in the version field. For comparison, the Flash Player reports " 11.7.700.203 "
ACTUAL -
In step 3, the applet does not run and an info bar says " Java(TM) was blocked because it is out of date " . Yet if you choose " Run this time " the applet will run and report the latest version.

In step 4, the entry for the java plugin has a pointless link to " Download Critical Security Update " and the Version field is blank.

REPRODUCIBILITY :
This bug can be reproduced always.