Arch Linux User Repository

Everyone who struggles to update right now: Please install the jdk21-openjdk package. It provides java-environment=21.

@shmilee: I like that idea. Implemented in 5.5-2 using JABREF_OPTIONS as variable name.

Note that you can then also put that environment variable into your .bashrc, .pam_environment or something similar to be automatically applied.

How about add an extra JavaOptions variable in launch script /usr/bin/jabref like this?

............
--module-path ${ROOT}/lib \
${JABREF_EXT_Options} \
--patch-module .............

So we can add the -Djdk.gtk.version=2 flag or -Dglass.gtk.uiScale=144dpi flag by cmdline, no need to edit /usr/bin/jabref after upgrade.

JABREF_EXT_Options='-Dglass.gtk.uiScale=144dpi -Djdk.gtk.version=2' jabref

Using JabRef with i3wm, I’m running into the issue described at https://github.com/JabRef/jabref/issues/5867 in which clicking the menu bar sometimes opens then immediately closes the associated menu, rendering it unusable.

I was able to fix this issue by adding the -Djdk.gtk.version=2 flag after line 9 in https://aur.archlinux.org/cgit/aur.git/tree/jabref.sh?h=jabref (as suggested in the related bug report https://bugs.openjdk.java.net/browse/JDK-8251240). This change also removes the “XSetErrorHandler() called with a GDK error trap pushed. Don't do that.” warning mentioned by ruiin in a previous comment.

So far, I have not encountered any adverse side-effect from this workaround.

@gothicVI: Did you update to version 5.11-2? This version will make sure that a full JDK is installed. Unfortunately, there is still the possibility to run into this issue because I forgot to update the jabref start script. It currently does not enforce the use of a JDK to run JabRef. So if you are still running into this issue with 5.11-2, please briefly report back. I'll release a 5.11-3 fixing this corner case then.

I have jre-openjdk installed and am experiencing the startup crash as well.

Thanks for the quick fix @Bevan. Is that a packaging issue for jre-openjdk? It seems like overkill that we need jdk-openjdk just for the missing module (as per your links). I just wonder if the jre-openjdk package is what needs the fix instead of this package.

@Rhinoceros: I could reproduce the issue. It looks like this issue exists since 2019 and was never fixed:

https://github.com/adoptium/adoptium-support/issues/12

https://github.com/javafxports/openjdk-jfx/issues/458

I'll change the runtime dependency from java-runtime to java-environment.

java-environment appears to be a (normal) dependency for me. If I have jre-openjdk installed, I get the following error, and jabref will not launch.

$ jabref
Error occurred during initialization of boot layer
java.lang.module.FindException: Module jdk.unsupported.desktop not found, required by javafx.swing

This is fixed if I install jdk-openjdk instead.

I don't think you need to bump pkgrel when fixing a FTBS with no effect on already build packages. People affected the build failure will notice without the pkgrel bump, and for everyone who already has the package built it'll just trigger a needless rebuild :)

@Bevan please always bump the pkgrel when updating...

@danieltetraquark: Done. Thanks for the notice!

@Bevan could you set gradle>7 as a build requirement, as it doesn't build with the gradle7 package?

@Bevan: I used (2) java-openjdk-bin, and Jabref has installed and works. At least, it starts and opens my files.