Package Details: jabref 5.13-1

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: 212
Popularity: 1.78
First Submitted: 2012-06-07 22:47 (UTC)
Last Updated: 2024-04-02 16:01 (UTC)

Dependencies (4)

Required by (0)

Sources (6)

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?

............
--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

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.

Latest Comments

« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 20 21 Next › Last »

Rhinoceros commented on 2018-01-08 09:30 (UTC)

That seems logical to me, too.

Bevan commented on 2018-01-08 09:28 (UTC)

Rhinoceros: That makes sense, yes. Hm... I could require java-openjfx=8 here since jabref currently only works with Java 8 anyway.

Rhinoceros commented on 2018-01-08 09:24 (UTC)

Oh yeah… I can see that now. I have no idea. Ahhh… perhaps it's because jre provides java-openjfx=9, and I already had that installed?

Bevan commented on 2018-01-08 07:53 (UTC)

Rhinoceros: How did you manage to install this package without installing java-openjfx first? It is a dependency.

Rhinoceros commented on 2018-01-08 04:00 (UTC)

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.

dvzrv commented on 2018-01-01 11:20 (UTC)

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

pryre commented on 2018-01-01 07:37 (UTC)

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.

Bevan commented on 2017-12-30 11:04 (UTC) (edited on 2017-12-30 11:04 (UTC) by Bevan)

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.

billypilgrim commented on 2017-12-30 10:19 (UTC)

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

Bevan commented on 2017-12-29 14:17 (UTC)

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