Whitelisting will be hard, since some of the problems are probably due
to threading problems between the OpenJDK, and the GTK thread used by
jayatana. So even if an application works fine on one JDK, it may be
broken on the next JDK. The whitelist would then need to check both, and
will need to be updated a lot.
Installing jayatana for the user to use "at own risk" is of course okay.
I still do think the way jayatana is injected into the JVM is bound to
repeatedly cause such trouble. A more reliable fix would probably be to
patch the JDK itself. It then would of course not apply to Oracle JDKs
(unless merged back by them), and require updates with new JDK versions.
The place to do this would probably be
"jdk/src/solaris/native/sun/awt/{swing_GTK*,gtk*}.c" and
"com/sun/java/swing/plaf/gtk/*.java"; or by implementing this as an
alternate "Unity" look-and-feel altogether.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441487
Title:
Running any Java program produces messages in the terminal, while
rendering many Java applications broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1441487/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
