Package Details: jabref 5.15-5

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: 217
Popularity: 0.34
First Submitted: 2012-06-07 22:47 (UTC)
Last Updated: 2026-02-03 22:03 (UTC)

Dependencies (4)

Required by (0)

Sources (11)

Pinned Comments

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 .. 14 15 16 17 18 19 20 21 22 23 Next › Last »

Rhinoceros commented on 2017-10-25 10:29 (UTC)

@Bevan Ah, fair enough. Thank you for the explanation.

Bevan commented on 2017-10-25 08:44 (UTC)

Rhinoceros: Currently this package uses a prebuilt jar-file. To apply the changes, this would have to be changed to build the jar-file from source on PKGBUILD. That is possible for sure, but then again there is also a jabref-git package here in the AUR which pretty much does exactly that. By the way: There are also prebuilt jar-files for the current git revision, but as far as I can see they only keep the most recent version on the server, so we cannot just use that: https://builds.jabref.org/master/

Rhinoceros commented on 2017-10-25 00:52 (UTC)

@Bevan Could you possibly backport the fixes into 4.0 instead? That's what normally happens on "official" Arch packages. You can get the fixes in patch format by appending `.patch` to the github urls that you list in your comment.

Zebra commented on 2017-10-07 17:16 (UTC)

Bevan: Reasonable enough. Thanks for maintaining!

Bevan commented on 2017-10-07 14:39 (UTC)

Zebra: Thanks for the feedback! The issue of not properly exiting is now fixed in git by the following three commits: https://github.com/JabRef/jabref/commit/7ef2b3a01687648d7cdeca1498551426117bdf84 https://github.com/JabRef/jabref/commit/85363d077e42c28ffe7b3cac7cd854c8c8786273 https://github.com/JabRef/jabref/commit/fae290caa38aedbea3a2d093419e5ade4e62d620 I'd like to wait for a release including these fixes before pushing JabRef 4 to AUR. The other issue of long starting time seemed to be an issue with leftover configuration from an older JabRef version, I could fix it by cleaning that up. Ogion: Good point, JabRef 4 uses JavaFX now so that package is required. I will add it as a dependency.

Ogion commented on 2017-10-07 13:53 (UTC)

The aur Package from your github link works just fine for me, except for one thing: I had to install `java-openjfx` from the repo, before JabRef would actually run. You should probably add that to the Depends.

Zebra commented on 2017-10-07 10:44 (UTC)

Bevan: I testet your package just now (4.0.1) and cannot reproduce your issues. Stops at once. start up time is 3.5 seconds max.

Bevan commented on 2017-10-04 16:51 (UTC) (edited on 2017-10-07 14:40 (UTC) by Bevan)

I have an update for JabRef 4.0 but I have serious issues with this version: * JabRef does not quit, it stays active after exit waiting for some futex. * On one machine JabRef needs many minutes to start, checking for duplicate aliases If you want to try the new package, you can get it from here: https://github.com/michaellass/AUR/tree/jabref-4/jabref I will only push it to the AUR as soon as those major issues are solved. Update: Problem no. 1 is now solved in git, problem no. 2 was a local issue with leftover data from older JabRef versions.

Bevan commented on 2017-08-24 08:14 (UTC)

koppor: Thanks for the updates! The new package release now explicitly calls java 8. I also looked into the .desktop file and the start script. The first has slightly different entries (Icon and StartupWMClass), so we cannot use it as is. But I changed the one provided by this package to be as close as possible. The start script provided here is very specific to Arch Linux as it calls archlinux-java to find out what JVM was selected by the user. So I'm not sure how valuable this is for upstream. It could be a starting point for a more universal start script that supports multiple distributions though.

koppor commented on 2017-08-18 08:26 (UTC)

JabRef will soon release version 4.0, which depends on JavaFX. I think, one has only to add "java-openjfx" to the list of dependencies. The java-runtime should be set to precisely 8, as JabRef currently does not run at Java9: https://github.com/JabRef/jabref/issues/2594

« First ‹ Previous 1 .. 14 15 16 17 18 19 20 21 22 23 Next › Last »