Narasimha-scandGitHub cbd625d57a desktop: fix "Failed to launch JVM" on Windows when Java Access Bridge is enabled (one cause of #4146) (#7260) ...

* desktop: bundle jdk.accessibility to fix "Failed to launch JVM" when assistive technologies are enabled (#4146)

The jlinked runtime shipped in desktop packages did not include the
jdk.accessibility module. On Windows, when Java Access Bridge is enabled
(jabswitch -enable, "Enable Java Access Bridge" in Ease of Access, or a
screen reader creating %USERPROFILE%\.accessibility.properties), AWT
throws AWTError "Assistive Technology not found:
com.sun.java.accessibility.AccessBridge" during Toolkit init, before any
window or log output, and the jpackage launcher reports "Failed to
launch JVM".

* docs: plan justifying jdk.accessibility fix for Windows JVM launch (#4146)

* desktop: bundle jdk.accessibility only when building the Windows package

2026-07-16 13:49:10 +01:00

..

src/jvmMain

desktop: prevent duplicate launches (#6979)

2026-05-18 09:15:20 +01:00

build.gradle.kts

desktop: fix "Failed to launch JVM" on Windows when Java Access Bridge is enabled (one cause of #4146) (#7260)

2026-07-16 13:49:10 +01:00