[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: "AtkWrapper not found" error impacting JOSM on Ubuntu/Mint



Hello,
The bug is closed so there is nothing to expect from OpenJDK. The solution must come from Debian or a new bug created.
The Java version which introduced the regression is 10.0.2+13-Ubuntu-1ubuntu0.18.04.1 because it contains the fix to move accessibility.properties in the "conf" folder. The issue did not occur before because the configuration file enabling ATK wrapper was not found by openjdk. A few hours after this version was delivered by Ubuntu we started to receive a dozen of bug reports, until I delivered a JOSM hotfix mitigating the issue.

Patching openjdk with your try/catch proposal and making the ATK wrapper a Recommends sounds a good idea.

Don't wait for openjdk guys for an answer: they simply don't care anymore with desktop technologies.

Cheers,
Vincent

Le ven. 24 août 2018 à 11:47, Samuel Thibault <sthibault@debian.org> a écrit :
Hello,

Vincent Privat, le mer. 22 août 2018 21:01:16 +0200, a ecrit:
> Samuel, do you know when the root issue will be fixed in Java ATK wrapper?

The root issue is in openjdk, not the wrapper. Openjdk has apparently
removed the way that was used to load the wrapper, without apparently
making sure that another way was implemented. I have forwarded the issue
upstream

http://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8204862

but apparently they don't have the issue (I guess they don't actually
manage to enable the wrapper in the configuration file).

> > > 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):

Which version is introducing the issue exactly?  AFAIK it's the whole
openjdk >= 9 which poses the problem.

> Has it ever been considered that this package is made optional rather than a
> strict dependency of openjdk-<n>-jre?

The problem is not the dependency, but what openjdk itself is doing. ATM
it seems to be insisting on loading the wrapper even when it's not
available.  I guess catching exceptions around
src/java.desktop/share/classes/java/awt/Toolkit.java's getDefaultToolkit
call to loadAssistiveTechnologies, to just print the exception but not
abort, would allow to make the dependency a Recommends only.

Concerning actually managing to load the wrapper, see the backlog of
#900912. I have commited to the git repo of java-atk-wrapper what is
said to be needed for making it loadable with openjdk 9 and later, but
as I said there, we still seem to be lacking in openjdk a path where the
wrapper can be put for openjdk to find it. And it's been a month without
anybody answering.

Samuel

Reply to: