Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#36082 - [icedtea-web-java7] Latest upgrade of openjdk7 to 2.4.1-1 breaks javaws

Attached to Project: Arch Linux
Opened by Richard Ullger (rullger) - Tuesday, 09 July 2013, 09:40 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Tuesday, 16 July 2013, 09:11 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Guillaume ALAUX (galaux)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 13
Private No


Following the upgrade of openjdk7 from 2.4.0-1 to 2.4.1-1 breaks javaws when opening a .jnlp file producing the following error...

$javaws itcharts.jnlp
Exception in thread "main" java.lang.NullPointerException
at javax.swing.SwingUtilities.appContextGet(
at javax.swing.SwingUtilities.getSharedOwnerFrame(
at javax.swing.JWindow.<init>(
at javax.swing.JWindow.<init>(
at net.sourceforge.jnlp.runtime.JNLPSecurityManager.<init>(
at net.sourceforge.jnlp.runtime.JNLPRuntime.initialize(
at Method)
at net.sourceforge.jnlp.runtime.Boot.main(

Reverting to openjdk7 2.4.0-1 packages resolves the issue.

Additional info:
* package version(s)
jdk7-openjdk 7.u40_2.4.1-1
jre7-openjdk 7.u40_2.4.1-1
jre7-openjdk-headless 7.u40_2.4.1-1
icedtea-web-java7 1.4-1
enlightenment17 0.17.3-1

* config and/or log files etc.
Running in an enlightenment environment.

Steps to reproduce:
Run a .jnlp file downloaded in chromium by right clicking and choosing run using icedteaweb or double-click the .jnlp file or run with javaws.
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Tuesday, 16 July 2013, 09:11 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed with patch, -2
Comment by Marcin Andrzejewski (mpan) - Tuesday, 09 July 2013, 12:47 GMT
Same happens in Firefox for applets embeded as JARs using <applet> element. After the exception plugin exits and Firefox hangs.

Seems that DE doesn't affect the issue, as I'm using latest xfce.

Package versions are the same, firefox 22.0.
Comment by André Fettouhi (A.Fettouhi) - Tuesday, 09 July 2013, 16:21 GMT
Can confirm this on KDE as well. DE seems unaffected by this bug.
Comment by rewpqighpoqiuer (pekka) - Tuesday, 09 July 2013, 16:46 GMT
Confirm this
chromium 28.0.1500.52-1
jdk7-openjdk 7.u40_2.4.1-1
icedtea-web-java7 1.4-1
Comment by Marcin Andrzejewski (mpan) - Tuesday, 09 July 2013, 18:42 GMT
It seems that for some reason `sun.awt.AppContext.getAppContext` returns erroneously `null` when an application is run wia JNLP. `javax.swing.SwingUtilities.appContextGet` attempts to call `get` on `null` and NPE occurs.

There is lots of reports of `getAppContext` returning `null` after u25, so I assume it's not Arch-specific bug and should be sent upstream.
Comment by gyurman (gyurman) - Thursday, 11 July 2013, 20:43 GMT
I have same
Comment by dangerginger (jkav77) - Thursday, 11 July 2013, 21:02 GMT
Same, also tried google-chrome and firefox. I have the problem in i3 and gnome.
Comment by Guillaume ALAUX (galaux) - Friday, 12 July 2013, 13:03 GMT
> so I assume it's not Arch-specific bug and should be sent upstream.

@rullger: please report this upstream
Comment by Richard Ullger (rullger) - Friday, 12 July 2013, 14:34 GMT
A bug report already exists upstream...
Comment by Guillaume ALAUX (galaux) - Friday, 12 July 2013, 14:37 GMT
Nice! I'm closing this one then. Thanks
Comment by Andrew Azores (aazores) - Monday, 15 July 2013, 15:23 GMT
A patch is available from upstream and the upstream maintainer for IcedTea-Web 1.4 does not have plans to create a new release for this patch alone. I've talked to him about it this morning and he has asked the package maintainers for other distros to incorporate the patch on their own.

Otherwise there may be quite a long wait before this fix makes it into a new release. Applying this with "patch -p1 < appContextFix.patch" in the PKGBUILD should be sufficient.