| Git Clone URL: | https://aur.archlinux.org/jabref.git (read-only, click to copy) |
|---|---|
| Package Base: | jabref |
| Description: | Graphical Java application for managing BibTeX and biblatex (.bib) databases |
| Upstream URL: | https://www.jabref.org/ |
| Licenses: | MIT |
| Submitter: | Allan |
| Maintainer: | Bevan |
| Last Packager: | Bevan |
| Votes: | 209 |
| Popularity: | 0.045356 |
| First Submitted: | 2012-06-07 22:47 (UTC) |
| Last Updated: | 2024-04-02 16:01 (UTC) |
Thankfully, version 5.8 of JabRef now builds with Java 17, i.e., you can use jdk17-openjdk from the official repositories to build this package. Hence, the following comment on JabRef 5.7 is obsolete:
Unfortunately, JabRef currently requires Java 18 to be built. This Java version is unsupported by now and is only available via AUR packages. For now I suggest installing jdk18-openj9-bin to be able to build this package.
@Bevan Thanks! xorg-xwayland did the trick for me
@conkeldurr: It's available in the AUR: https://aur.archlinux.org/packages/archlinux-java-run
Got the following error-
$ makepkg -si
==> Making package: jabref 5.7-1 (Thu 22 Sep 2022 03:22:58 PM EDT)
==> Checking runtime dependencies...
==> Installing missing dependencies...
error: target not found: archlinux-java-run>=7
==> ERROR: 'pacman' failed to install missing dependencies.
==> Missing dependencies:
-> archlinux-java-run>=7
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.
@MadMe: As far as I can see, Java still relies on X11 and does not support Wayland directly. Do you have xorg-xwayland installed? If not, could you please check if installing that package (and maybe restarting your graphical session) solves the problem for you?
I've got an problem. Jabref refuses to start on Wayland (sway)
i get the following error:
Exception in thread "main" java.lang.UnsupportedOperationException: Unable to open DISPLAY
Any Ideas?
@Flupp: The tar is created during build, so it's not coming from upstream directly. Weirdly, I cannot reproduce your problem:
tar tvf src/jabref-5.6/build/distributions/JabRef-5.6.tar | grep codec
-rw-r--r-- 0/0 335042 2020-03-29 19:14 JabRef-5.6/lib/commons-codec-1.11.jar
And similarly, it's correct in pkg as well:
ls -la pkg/jabref/usr/share/java/jabref/lib/commons-codec-1.11.jar
-rw-r--r-- 1 bevan bevan 335042 6. Mai 20:25 pkg/jabref/usr/share/java/jabref/lib/commons-codec-1.11.jar
I wonder if this depends on the Java version used during the build step. Maybe gradle fetches different sources then. When running makepkg, there will be an output like the following:
Using JDK from /usr/lib/jvm/java-18-openjdk to build JabRef.
What does it say in your case?
Currently (version 5.6-1) I get:
java.lang.module.FindException: java.io.FileNotFoundException: /usr/share/java/jabref/lib/commons-codec-1.11.jar (Permission denied)
It seems this file comes from the line
tar xf distributions/JabRef-${pkgver}.tar -C "${pkgdir}"/usr/share/java/${pkgname} JabRef-${pkgver}/lib --strip-components=1
in the PKGBUILD. Actually, I am not sure if this is a packaging issue or an upstream issue since the permission is already wrong in the tar (600).
@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
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/jabreflike this?So we can add the
-Djdk.gtk.version=2flag or-Dglass.gtk.uiScale=144dpiflag by cmdline, no need to edit/usr/bin/jabrefafter 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=2flag 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.