After applying Java Updates, KeyMusician Keyboard application won't run

Bug #1790228 reported by Aere Greenway
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
java-common (Ubuntu)
New
Undecided
Unassigned

Bug Description

After applying the latest Java updates (to open Java), the Keymusician Keyboard application no longer runs.

When I run the JAR file manually in a terminal, I get the following error information:

aere@aere-VGN-SZ430N:~$ java -jar KMK.jar -DebugLevel=2373
Exception in thread "main" java.awt.AWTError: Assistive Technology not found: org.GNOME.Accessibility.AtkWrapper
 at java.desktop/java.awt.Toolkit.newAWTError(Toolkit.java:472)
 at java.desktop/java.awt.Toolkit.fallbackToLoadClassForAT(Toolkit.java:488)
 at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
 at java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)
 at java.base/java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1608)
 at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
 at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
 at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
 at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
 at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
 at java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:497)
 at java.desktop/java.awt.Toolkit.loadAssistiveTechnologies(Toolkit.java:532)
 at java.desktop/java.awt.Toolkit.getDefaultToolkit(Toolkit.java:613)
 at java.desktop/sun.swing.SwingUtilities2.getSystemMnemonicKeyMask(SwingUtilities2.java:2143)
 at java.desktop/javax.swing.plaf.basic.BasicLookAndFeel.initComponentDefaults(BasicLookAndFeel.java:1096)
 at java.desktop/javax.swing.plaf.metal.MetalLookAndFeel.initComponentDefaults(MetalLookAndFeel.java:440)
 at java.desktop/javax.swing.plaf.basic.BasicLookAndFeel.getDefaults(BasicLookAndFeel.java:150)
 at java.desktop/javax.swing.plaf.metal.MetalLookAndFeel.getDefaults(MetalLookAndFeel.java:1560)
 at java.desktop/javax.swing.UIManager.setLookAndFeel(UIManager.java:587)
 at java.desktop/javax.swing.UIManager.setLookAndFeel(UIManager.java:628)
 at pkgamk.AMKClass.main(AMKClass.java:121)
Caused by: java.lang.ClassNotFoundException: org.GNOME.Accessibility.AtkWrapper
 at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
 at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:190)
 at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
 at java.base/java.lang.Class.forName0(Native Method)
 at java.base/java.lang.Class.forName(Class.java:374)
 at java.desktop/java.awt.Toolkit.fallbackToLoadClassForAT(Toolkit.java:485)
 ... 19 more
aere@aere-VGN-SZ430N:~$

However, when I run the same JAR-file using Java Web Start (iced-tea), it runs okay, using the same configuration.

When running it via Java Web Start, it appears the earlier problem I reported, regarding the lack of slider-handles using the GTK+ look-and-feel, has been fixed.

I am using Lubuntu 18.04.1 LTS.

On that system, default-jre depends on openjdk-11-jre, version 10.0.2+13-1ubuntu0.18.04.1

When I accessed the installed application (installed by gdebi), I expected to run as it had been doing before.

Instead, it crashed early in the initialization process.

I tried running it manually in a terminal session, and got the error reported above.

I tried running it via JNLP (Java Web Start, using icedtea), and it ran okay.

Since it is now distributed as a Debian package, I need the installed version to continue to work.

I can attach (if you request), the Debian package for installing it, the JAR-file, and/or the JNLP file for launching it via Java Web Start.

Please let me know what you need.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: default-jre 2:1.10-63ubuntu1~02
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: LXDE
Date: Fri Aug 31 15:40:58 2018
InstallationDate: Installed on 2018-06-28 (64 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: java-common
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Aere Greenway (aere) wrote :
Revision history for this message
Aere Greenway (aere) wrote :

I tested on Ubuntu 18.04.1 LTS (in addition to Lubuntu 18.04.1 LTS), and the same problem occurred.

Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Based on the error message in the stacktrace this is the same issue as reported in bug 1788250, so it I'm marking this as a duplicate. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.