Comment 36 for bug 1441487

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.