I remember too, it was indeed a nightmare and I don't want to live that again.It took me a while but I found a workaround that doesn't need any user action nor any adherence to ATK wrapper.We can just catch the AWTError and try again to re-create our MainFrame. As the ATK initialization fails only after the AWT toolkit has been created, the second call succeeds:Kevin, can you please check tomorrow that it works for you too?I'm leaving the ticket open a few days as we will probably receive many more bug reports this week.Right now it's too difficult to disable ATK on Java 10 and remain compatible with Java 8. I'll revisit this topic once we migrate to Java 11.Cheers,VincentLe mer. 22 août 2018 à 01:14, Kevin Kenny <kevin.b.kenny@gmail.com> a écrit :On Tue, Aug 21, 2018 at 5:48 PM Vincent Privat
<vincent@josm.openstreetmap.de> wrote:
>
> I found this bug:
> https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1788250
> Vincent
>
> Le mar. 21 août 2018 à 23:27, Vincent Privat <vincent@josm.openstreetmap.de>
> a écrit :
>
> > Hello,
> > Since today we are spammed by bug reports from Linux Mint and Ubuntu when
> > people try to launch JOSM with the latest Java update
> > (10.0.2+13-Ubuntu-1ubuntu0.18.04.1):
> >
> > https://josm.openstreetmap.de/ticket/16666
> >
> > The error is "ClassNotFoundException: org.GNOME.Accessibility.AtkWrapper".
> >
> > Is it a known issue? We cannot really workaround it unless telling every
> > impacted user to manually disable ATK wrapper in accessibility.properties.
> >
> > Thanks,
> > Vincent
> >
Even deleting the ATK wrapper in accessibility.properties doesn't help,
you also have to launch JOSM with a command like
java -Xmx1g -Xbootclasspath/a:/usr/share/java/java-atk-wrapper.jar
-jar ~/josm/josm-tested.jar
When I do both things, it appears to work around the problem.
AtkWrapper is a nightmare. I remember when
https://josm.openstreetmap.de/ticket/12022
had me using Meerkartor for a while.