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

Rhinoceros commented on 2017-01-23 00:16 (UTC)

It looks like jabref.sh selects the latest version of java installed, rather than following the default, as set in archlinux-java. This can cause problems, because it selects the buggy version in my case [1]. I understand that jabref needs java 8, not java 7, but it might be worth following archlinux-java if a version 8 is selected, otherwise defaulting to one of the version 8s. Hard-coding the version seems wrong IMO. [1] https://bugs.archlinux.org/task/52625

danmc commented on 2016-12-15 15:57 (UTC)

The license has changed to MIT since version 3.6.

Bevan commented on 2016-07-16 09:23 (UTC)

@antony: This issue occured when there was already a "src" directory lying around from the last build. I now changed the PKGBUILD to only extract from the JAR what is needed which solves this issue.

anntzer commented on 2016-07-16 01:16 (UTC)

Cuurently fails to build: ==> Extracting sources... -> Extracting JabRef-3.5.jar with bsdtar com/: Can't replace existing directory with non-directory <elided> META-INF/maven/org.apache.httpcomponents/httpcore-nio/: Can't replace existing directory with non-directory bsdtar: Error exit delayed from previous errors. ==> ERROR: Failed to extract JabRef-3.5.jar Aborting... :: failed to build jabref package(s)

Bevan commented on 2016-07-15 22:20 (UTC)

@chicomag: The .jar file needs to be extracted because this is where we get the application icon get from, so extracting is actually intended. I don't see any disadvantage of this, because we package only what is needed (jar file, icon, start script, desktop file).

chicomag commented on 2016-07-15 22:00 (UTC)

Please, add noextract=("JabRef-${pkgver}.jar") to the PKGBUILD, because makepkg is extracting the file, and this is not intended.

koppor commented on 2016-06-05 17:43 (UTC)

BibLaTeX mode is a file-based mode now. Switch the mode using File -> "Switch to BibLaTeX mode". See also blog entry "April 19, 2016 – Release of JabRef 3.3" on http://www.jabref.org/blog/. (Sorry, currently no deep links possible).

Bevan commented on 2016-04-19 20:36 (UTC)

@Moneysac: Will push the new version in a moment but please use the "flag out-of-date" function in future. Regarding the BibLaTeX mode: I think the option just moved. In Preferences->General you can change the standard mode from BibTeX to BibLaTeX.

Moneysac commented on 2016-04-19 11:25 (UTC)

Version 3.3 is available. This package does not provide the biblatex mode which is important for online references.

anntzer commented on 2016-02-04 08:58 (UTC) (edited on 2016-02-04 08:58 (UTC) by anntzer)

jabref.sh should just force Java 8 (like the jabref-git package does: https://aur.archlinux.org/cgit/aur.git/tree/jabref.sh?h=jabref-git), otherwise jabref will fail to start on environments where Java 7 is the default.

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