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.

The new version failed to start on my system with:

Error: Could not find or load main class org.jabref.JabRefMain

I'm using java-8-openjdk. After installing java-openjfx, jabref could again launch.

@Bevan: it was the license file. Deleted and reinstalled.

I was also having some issues building the package. Cleaned out the cache of my AUR helper, then had no issues installing it. Might have something strange going on with scrap files from between versions, but it was a simple fix.

curl https://raw.githubusercontent.com/JabRef/jabref/v4.1/LICENSE.md 2>/dev/null | sha256sum : d0a8248eeaafc526f1137703fdc5aac1c8fae106f94c4bef56e3650e2c4c73a7

... which is exactly the checksum given in the PKGBUILD. Even in upstream's master branch the file was not touched since May: https://github.com/JabRef/jabref/commits/master/LICENSE.md

billypilgrim and dvzrv: Maybe you have still an old file from JabRef 3 lying around? If necessary, please download the file manually and check where the difference is coming from.

This package is no longer building as LICENSE.md has changed

dvzrv: They do for me. I just rechecked. Maybe one of the downloads failed / got corrupted?

@Bevan: The checksums don't match

If you use the current version (4.1-1) be sure to always have a backup of your bib files as it randomly overwrites entries when editing.

Java 9 support would be nice. Just need to add '--add-modules java.xml.bind' to the command line if Java 9 is used.

Since people keep commenting without reading through the comments before, here's a summary on why this is not updated to JabRef 4.0: - JabRef 4.0 has a series of serious bugs (won't start, won't stop, will eat gigabytes of memory, ...). - Most of these bugs are fixed in git by now but no release includes them yet. - Applying these patches to this package would require everyone to rebuild the JAR file and install several build-time dependencies. - People wanting to build the JAR from current git can use the jabref-git package here in AUR. - There is no need to duplicate jabref-git in this package, it is already there. Use it. - If you really really want to install JabRef 4.0 without these patches, take this PKGBUILD: https://github.com/michaellass/AUR/tree/jabref-4/jabref - You can also download a prebuilt jar file from https://builds.jabref.org/master/ - Unfortunately these jar files are not archived which is why I cannot use them here. Please refrain from asking why this has not been updated yet, why I do not apply patches from git, or when I will update this package. I will likely just ignore these questions in future.