Thanks, that was the solution :-) I first tried downgrading libatk-wrapper-java and libatk-wrapper-java-jni to the 0.30 version in stable, which also fixed the issues. But disabling assistive technologies in /etc/java-8-openjdk/accessibility.properties like you suggested (it was enabled before) also fixes the issues with libatk-wrapper-java 0.33 \o/
Thanks! - Roland On 06.04.2016 21:13, Sebastiaan Couwenberg wrote: > Control: tags -1 moreinfo > > Hi Roland, > > Sorry to hear about your issue, although I have experienced it myself in > the past too. > > On 04/06/2016 08:34 PM, Roland Hieber wrote: >> at >> org.GNOME.Accessibility.AtkWrapper$5.dispatchEvent(AtkWrapper.java:697) > > The above is a big red flag, it suggests the GNOME ATK bridge is causing > the issue. This should be fixed according to #813143. > > I can only reproduce your issue when I uncomment the > assistive_technologies option in > /etc/java-8-openjdk/accessibility.properties: > > # > # The following line specifies the assistive technology classes > # that should be loaded into the Java VM when the AWT is initailized. > # Specify multiple classes by separating them with commas. > # Note: the line below cannot end the file (there must be at > # a minimum a blank line following it). > # > #assistive_technologies=org.GNOME.Accessibility.AtkWrapper > > I thought this was disabled by default again, but it seems the fixes in > java-atk-wrapper (0.33.3-6) weren't sufficient. > > Can you confirm that disabling the option fixes this issue in JOSM for > you too? > > Kind Regards, > > Bas
