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

dvzrv commented on 2017-12-29 14:01 (UTC)

@Bevan: The checksums don't match

j0hannes commented on 2017-12-27 17:17 (UTC)

If you use the current version (4.1-1) be sure to always have a backup of your bib files as it randomly overwrites entries when editing.

Huulivoide commented on 2017-12-10 15:13 (UTC)

Java 9 support would be nice. Just need to add '--add-modules java.xml.bind' to the command line if Java 9 is used.

Bevan commented on 2017-11-25 18:48 (UTC)

Since people keep commenting without reading through the comments before, here's a summary on why this is not updated to JabRef 4.0: - JabRef 4.0 has a series of serious bugs (won't start, won't stop, will eat gigabytes of memory, ...). - Most of these bugs are fixed in git by now but no release includes them yet. - Applying these patches to this package would require everyone to rebuild the JAR file and install several build-time dependencies. - People wanting to build the JAR from current git can use the jabref-git package here in AUR. - There is no need to duplicate jabref-git in this package, it is already there. Use it. - If you really really want to install JabRef 4.0 without these patches, take this PKGBUILD: https://github.com/michaellass/AUR/tree/jabref-4/jabref - You can also download a prebuilt jar file from https://builds.jabref.org/master/ - Unfortunately these jar files are not archived which is why I cannot use them here. Please refrain from asking why this has not been updated yet, why I do not apply patches from git, or when I will update this package. I will likely just ignore these questions in future.

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.

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