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.

Thanks @gothicVI. I just pushed a new version (5.11-3) that should fix the issue. If it does not, please report back.

@Bevan here you go. I can ammend the post this evening with the same output from the machines where it's working.

$ /usr/bin/archlinux-java-run -a 21 -b 21 -- -version
openjdk version "21" 2023-09-19
OpenJDK Runtime Environment (build 21+35)
OpenJDK 64-Bit Server VM (build 21+35, mixed mode, sharing)
$ /usr/bin/archlinux-java-run -a 21 -b 21 -f jdk -- -version
openjdk version "21.0.1" 2023-10-17
OpenJDK Runtime Environment (build 21.0.1+12-29)
OpenJDK 64-Bit Server VM (build 21.0.1+12-29, mixed mode, sharing)

@gothicVI: I have a strong suspicion what the problem is but I would like to make sure before pushing a new package version to everyone. Could you please run the following two commands and post the output here?

/usr/bin/archlinux-java-run -a 21 -b 21 -- -version

/usr/bin/archlinux-java-run -a 21 -b 21 -f jdk -- -version

If those create different outputs, you may try and edit /usr/bin/jabref and modify line 17 accordingly (i.e., adding '-f jdk' before the '--'). If that fixes your issues that would be great to know.

@Bevan I just reinstalled - still the same outcome. All java related packages installed are:

$ yay -Qs .*java.*
local/archlinux-java-run 10-1
    Java Application Launcher for Arch Linux
local/ca-certificates-utils 20220905-1
    Common CA certificates (utilities)
local/cjs 6.0.0-1
    Javascript Bindings for Cinnamon
local/duktape 2.7.0-6
    Embeddable Javascript engine
local/jabref 5.11-2
    Graphical Java application for managing BibTeX and biblatex (.bib) databases
local/java-environment-common 3-5
    Common files for Java Development Kits
local/java-openjdk-bin 21.0.1.u12-1
    Java OpenJDK 21.0.1 Oracle Build.
local/java-runtime-common 3-5
    Common files for Java Runtime Environments
local/jdk8-openjdk 8.392.u08-1
    OpenJDK Java 8 development kit
local/jdownloader2 latest-17
    Download manager, written in Java, for one-click hosting sites like Rapidshare and Megaupload. Uses its own updater.
local/jre-openjdk 21.u35-8
    OpenJDK Java 21 full runtime environment
local/jre8-openjdk 8.392.u08-1
    OpenJDK Java 8 full runtime environment
local/jre8-openjdk-headless 8.392.u08-1
    OpenJDK Java 8 headless runtime environment
local/js102 102.15.0-1
    JavaScript interpreter and libraries - Version 102
local/qt5-declarative 5.15.11+kde+r32-1 (qt5)
    Classes for QML and JavaScript languages
local/qt5-webchannel 5.15.11+kde+r3-1 (qt5)
    Provides access to QObject or QML objects from HTML clients for seamless integration of Qt applications with HTML/JavaScript clients
local/qt6-declarative 6.6.0-1 (qt6)
    Classes for QML and JavaScript languages
local/webkit2gtk 2.42.2-1
    Web content engine for GTK
local/webkit2gtk-4.1 2.42.2-1
    Web content engine for GTK

No issues on two other machines where I have jdk-openjdk instead of jre-openjdk installed. Does this change something?

@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 :)