Sure. In the update to 5.11-2 I added java-environment=21 as a dependency to make sure that people have a full JDK in version 21 installed. However, I forgot to also adjust the start script to enforce that this full JDK is used to launch JabRef.
I assumed that people would have installed either a full JDK or a JRE. However, in your case you have installed both (java-openjdk-bin as a JDK and jre-openjdk as JRE). Hence, the dependency was fulfilled but JabRef was still started with the JRE instead of the JDK. I now updated the start script so that the JDK is used.
Pinned Comments
Bevan commented on 2024-03-28 17:57 (UTC)
Everyone who struggles to update right now: Please install the jdk21-openjdk package. It provides java-environment=21.
Bevan commented on 2022-03-14 20:04 (UTC)
@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.
shmilee commented on 2022-03-12 13:51 (UTC)
How about add an extra JavaOptions variable in launch script
/usr/bin/jabref
like this?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.matteodelabre commented on 2020-11-17 14:25 (UTC)
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.