Package Details: jabref 5.15-2

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.23
First Submitted: 2012-06-07 22:47 (UTC)
Last Updated: 2024-09-23 19:59 (UTC)

Dependencies (4)

Required by (0)

Sources (7)

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

d4muck commented on 2017-11-25 10:33 (UTC)

@Bevan when will you update to v4? As I understood you wrote in your pinned comment that you solved both issues

Bevan commented on 2017-11-13 10:28 (UTC)

hseara: This looks to me like another instance of JabRef is running but has somehow crashed. Could you check for any running java instances with ps and kill them if they relate to jabref? Or, alternatively, reboot.

hseara commented on 2017-11-13 10:20 (UTC) (edited on 2017-11-13 10:45 (UTC) by hseara)

@Bevan Thanks your suggestion. If you cannot open jabref and you get the following message: 11:16:21.281 [AWT-EventQueue-0] WARN org.jabref.logic.remote.server.RemoteListenerServerLifecycle - Port is blocked java.net.BindException: Address already in use (Bind failed) .... 11:16:21.357 [AWT-EventQueue-0] INFO org.jabref.JabRefMain - Arguments passed on to running JabRef instance. Shutting down. check for open instances of jabref and kill them. Note: In multi-user system environments check the following issue: (https://github.com/JabRef/jabref/issues/2282)

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.

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