#1025830 beauti2 fails to start

#1025830#5
Date:
2022-12-10 06:44:32 UTC
From:
To:
Hi,

When launching
$ beauti2
I get the exception message discussed in bug #1025829, then a window from the
beast package manager, then the program terminates.
In the console I have

Graphics Device initialization failed for :  es2, sw
Error initializing QuantumRenderer: no suitable pipeline found
java.lang.RuntimeException: java.lang.RuntimeException: Error initializing QuantumRenderer: no suitable pipeline found
        at com.sun.javafx.tk.quantum.QuantumRenderer.getInstance(QuantumRenderer.java:280)
        at com.sun.javafx.tk.quantum.QuantumToolkit.init(QuantumToolkit.java:222)
        at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:261)
        at com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:267)
        at com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:158)
        at com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:658)
        at com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:678)
        at com.sun.javafx.application.LauncherImpl.lambda$launchApplication$2(LauncherImpl.java:195)
        at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.lang.RuntimeException: Error initializing QuantumRenderer: no suitable pipeline found
        at com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.init(QuantumRenderer.java:94)
        at com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:124)
        ... 1 more
java.lang.reflect.InvocationTargetException
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:568)
        at beast.pkgmgmt.launcher.BeastLauncher.run(Unknown Source)
        at beast.pkgmgmt.launcher.BeautiLauncher.main(Unknown Source)
Caused by: java.lang.RuntimeException: No toolkit found
        at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:273)
        at com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:267)
        at com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:158)
        at com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:658)
        at com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:678)
        at com.sun.javafx.application.LauncherImpl.lambda$launchApplication$2(LauncherImpl.java:195)
        at java.base/java.lang.Thread.run(Thread.java:833)

so probably there is an issue when loading openjfx. I whall investigate shortly
but nevertheless drop this bug so that it does not get forgotten.

Cheers,

#1025830#10
Date:
2022-12-18 14:15:28 UTC
From:
To:
Hello,

I tried to investigate further, I feel a window should appear and the
action of the user is expected, yet I don't see anything except the
initial "Initializing BEAUti..." GUI.
My knowledge of jdb did not allow me to understand further what is going on.

Cheers,

#1025830#17
Date:
2023-12-07 17:33:49 UTC
From:
To:
Hi,

Am Sun, Dec 18, 2022 at 03:15:28PM +0100 schrieb Pierre Gruet:

I tried to verify the issue with the latest uploaded beast2-mcmc and get:

$ beauti2
Loading package BEAST.base v2.7.6

as well as the very small "Initializing BEAUti..." window.

So this issue persists and some help to track this down would be really
appreciated.

Kind regards
    Andreas.

#1025830#20
Date:
2026-11-01 18:53:44 UTC
From:
To:
Hello,

Bug #1025830 in beast2-mcmc reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/med-team/beast2-mcmc/-/commit/4b0fae180ba2025399ff9fcd2dfdd9904ac0ffd9
BEAUti hung forever on its "Initialising BEAUti . . ." splash screen
because the package only installed BEAST.base's version.xml.  BEAST.app
ships its own version.xml listing the services it provides, including
beastfx.app.inputeditor.InputEditor.  Without it
PackageManager.listServices("beastfx.app.inputeditor.InputEditor")
returned null, InputEditorFactory.init() threw a NullPointerException
and the JavaFX start-up Task ended up FAILED, but Beauti only listens
for SUCCEEDED, so the splash screen stayed up.

Install beastfx/version.xml as beast.app.version.xml and make the
Debian-specific lookup in BEASTClassLoader also register that file from
/usr/share/beast2-mcmc.
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1025830

#1025830#27
Date:
2026-11-01 19:12:50 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
beast2-mcmc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1025830@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille <tille@debian.org> (supplier of updated beast2-mcmc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sun, 01 Nov 2026 18:58:28 +0100
Source: beast2-mcmc
Architecture: source
Version: 2.7.8+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team <debian-med-packaging@lists.alioth.debian.org>
Changed-By: Andreas Tille <tille@debian.org>
Closes: 1025830
Changes:
 beast2-mcmc (2.7.8+dfsg-2) unstable; urgency=medium
 .
   * Install the BEAST.app version.xml as beast.app.version.xml and register
     its services at start-up
     Closes: #1025830
   * Reflow Uploaders field (cme)
   * debputy lint --auto-fix (routine-update)
Checksums-Sha1:
 58f897787a4c92eb50cf58e22df2b15a13b387ce 2746 beast2-mcmc_2.7.8+dfsg-2.dsc
 f398d691476a8fc76c8c7a5d524a9e74826fe225 16756 beast2-mcmc_2.7.8+dfsg-2.debian.tar.xz
 b8a6cdaad98e3eff90d67da9d6284c1e5ddebd64 15610 beast2-mcmc_2.7.8+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 d38748a8c3aa8a659e7893c317fec9825cfeedd84d34f2021cf6b536a00661ed 2746 beast2-mcmc_2.7.8+dfsg-2.dsc
 279ec374a5649891ad097fea454d4e5ed9d9d0e79be2f2286e1f0b4cb0f473e9 16756 beast2-mcmc_2.7.8+dfsg-2.debian.tar.xz
 6edd423b3cb7232a6f2e02d7ae401e58563f0994632a93523255ae4beda6709e 15610 beast2-mcmc_2.7.8+dfsg-2_amd64.buildinfo
Files:
 7c29027fa3ddb757d42d923717298319 2746 science optional beast2-mcmc_2.7.8+dfsg-2.dsc
 d84429f700c666f436adffe4d5aa8326 16756 science optional beast2-mcmc_2.7.8+dfsg-2.debian.tar.xz
 4f32015e804c674dd5d0f46ca87a1755 15610 science optional beast2-mcmc_2.7.8+dfsg-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmrnin0RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEVeRAAm+zcXqTJk3UqRzaTFzElpGD7XIRfrU4m
kEtALm8dRKQjTYTwR1jxRpGWFvIgct8/J9McvejL+Ivc/FUiUe8IgmtF8d0eOopU
7B1qEAd5MOlO67UKSej3C0Wtz4YJteQAhRUVGUhWhDquKktewJHPzcxnZNLJY1eo
wn2j1mAqhrw1Bz90X188ZgVRrMjc3u6VM0VrfBeGk8vQPmv4wUMdxswKbfr7UYlX
ylBW1jLW69U2JvvM+p41lWq/Ap+jNl/08b57NIKrxPmHz7pW/lGHx4qCVMyMy8/j
QbiQBQscrB9gM6gJS3lS+FVLkRXABTwp2469qh5ik2/utlVrEsA8c8nXU6pMqSXm
c45IDoVIttX2DpwJL1crp73jHDFmbxJncNDs42RmNPK0AUtKptCr7UJ2BgqEenoM
eDjiRSxKWL35H078lXWy1jjERb7zWXOFX5QHpKdtVZK+w1Dp0rmFPvo5RBgtpTx4
dpObPzNT19te1BKYGP69BkY4zOEvra823tZaB1d6qic1/FWK5/LFJU88IbDZrD00
an3wjQpJuI/JvmDYpJie+r67jVRYzyrZgxjaoqxE/EwJ+RDXkmWTwVVQDzx8Nlrr
sdx12K0KCQZfcSOmuddJPzCmlJlOqiMaPRlO7CtFWRzGsaQ8Jhyj6I7g/pvvpLzb
FXX0uyNZrGs=
=RDxD
-----END PGP SIGNATURE-----