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.

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.

@Vitrum-cnkj34kr8: Unfortunately, none of those options is the one I would suggest. "jdk-openjdk" (https://archlinux.org/packages/extra/x86_64/jdk-openjdk/) is the JDK included in the Arch repositories and it provides java-environment 21. So maybe just go ahead and install jdk-openjdk manually before building this package.

On update, it asks me to choose a java-environment. Which one is the correct?

:: There are 8 providers available for java-environment=21:
1) amazon-corretto-21-bin
2) java-openjdk-bin
3) jdk
4) jdk-openjdk-xdg
5) jdk21-jetbrains-bin
6) jdk21-jetbrains-imfix
7) liberica-jdk-full-bin
8) zulu-21-bin

The reason why I could not reproduce the issue is that I had jdk-temurin installed which currently is still at version 20. This means that gradle somehow tries to find a JDK matching the version specified as toolchain, no matter what we set via archlinux-java-run as $JAVA_HOME.

The best solution I can think of right now is exactly what Pavlov suggested: setting the toolchain in build.gradle to version 21 and forcing the use of JDK 21 for compilation and execution of JabRef. This is what I just pushed as jabref 5.10-2.

If anyone has a suggestion how we can avoid this issue while being more flexible with the JDK versions, please leave a comment.

Thanks Pavlov! By replicating your exact setup I am now able to reproduce the issue. I'll try to find the root cause.