@n.vaughan You just needed to follow the pinned comment. It looks like you are using the old PKGBUILD. The current one already has that line in it!
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=jabref#n16
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: | 213 |
Popularity: | 0.067418 |
First Submitted: | 2012-06-07 22:47 (UTC) |
Last Updated: | 2025-01-17 16:00 (UTC) |
« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 19 .. 22 Next › Last »
@n.vaughan You just needed to follow the pinned comment. It looks like you are using the old PKGBUILD. The current one already has that line in it!
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=jabref#n16
@Rhinoceros, I just changed the line:
depends=('archlinux-java-run>=4' 'java-openjfx'
to:
depends=('archlinux-java-run>=4' 'java8-openjfx'
in the PKGBUILD file. It now works fine.
@n.vaughan It's in the official repos, not the AUR. Did you follow the pinned comment? pacman -Syu
then pacman -S --asdeps java8-openjfx
I couldn't find java8-openjfx in the AUR, only java-openjfx. The install failed.
Thank you for the quick update!
Important note on the java-openjfx update:
Arch restructured the java-openjfx package. Version 8 which is required by jabref is now called java8-openjfx. To update your system, you need to temporarily uninstall jabref, then make a full system update and finally build and install the newest version:
The change has reached the stable repos now.
# pacman -Syu
...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing java-openjfx (11.0.3.u1-1) breaks dependency 'java-openjfx<9' required by jabref
That we get openjfx for newer Java versions is great news! I'll update the dependencies for this package as soon as the change reaches the stable repos. People using testing that want to install openjfx 11 probably need to modify this package to get around dependency issues.
There is a new package (currently in testing): java8-openjfx. I think (at least when java8-openjfx leaves testing) this package should depend on that package, as java-openjfx was upgraded to java 11.
Sorry for the late response, I didn't have notifications enabled. Both of your commands give the same output:
openjdk version "1.8.0_202" OpenJDK Runtime Environment (build 1.8.0_202-b26) OpenJDK 64-Bit Server VM (build 25.202-b26, mixed mode)
At the moment, I am using the latest jar file provided at "https://builds.jabref.org/master/"! This seems to work better.
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.