Package Details: jabref 5.15-4

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: 216
Popularity: 0.36
First Submitted: 2012-06-07 22:47 (UTC)
Last Updated: 2025-10-09 18:38 (UTC)

Dependencies (4)

Required by (0)

Sources (10)

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

1 2 3 4 5 6 .. 23 Next › Last »

Bevan commented on 2025-10-09 18:38 (UTC)

@Hexamotion: All current build issues should be fixed in version 5.15-4.

Bevan commented on 2025-10-08 19:12 (UTC) (edited on 2025-10-08 19:40 (UTC) by Bevan)

@Hexamotion: Thanks for the report. I was able to reproduce the problem here. I'll take a closer look at it, but it will probably take a day or two.

Quick update: A solution is to modify build.gradle and to replace

reports.html.outputLocation.set(file("${reporting.baseDir}/${name}"))

by

reports.html.outputLocation.set(file("${reporting.getBaseDirectory()}/${name}"))

However, there are more build issues right now:

> Could not resolve all files for configuration ':compileClasspath'.
   > Could not find com.tobiasdiez:easybind:2.2.1-SNAPSHOT.
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/com/tobiasdiez/easybind/2.2.1-SNAPSHOT/maven-metadata.xml
       - https://repo.maven.apache.org/maven2/com/tobiasdiez/easybind/2.2.1-SNAPSHOT/easybind-2.2.1-SNAPSHOT.pom
       - https://oss.sonatype.org/content/groups/public/com/tobiasdiez/easybind/2.2.1-SNAPSHOT/maven-metadata.xml
       - https://oss.sonatype.org/content/groups/public/com/tobiasdiez/easybind/2.2.1-SNAPSHOT/easybind-2.2.1-SNAPSHOT.pom
       - https://s01.oss.sonatype.org/content/repositories/snapshots/com/tobiasdiez/easybind/2.2.1-SNAPSHOT/maven-metadata.xml
       - https://s01.oss.sonatype.org/content/repositories/snapshots/com/tobiasdiez/easybind/2.2.1-SNAPSHOT/easybind-2.2.1-SNAPSHOT.pom
       - https://jitpack.io/com/tobiasdiez/easybind/2.2.1-SNAPSHOT/maven-metadata.xml
       - https://jitpack.io/com/tobiasdiez/easybind/2.2.1-SNAPSHOT/easybind-2.2.1-SNAPSHOT.pom
       - https://sandec.jfrog.io/artifactory/repo/com/tobiasdiez/easybind/2.2.1-SNAPSHOT/maven-metadata.xml
       - https://sandec.jfrog.io/artifactory/repo/com/tobiasdiez/easybind/2.2.1-SNAPSHOT/easybind-2.2.1-SNAPSHOT.pom
     Required by:
         root project 'JabRef'

An update to easybind 2.3.0 might solve that: https://github.com/JabRef/jabref/pull/13433

Hexamotion commented on 2025-10-08 16:03 (UTC)

I am unable to install jabref.

I am getting a similar error like this:

> Configure project :
Project : => 'org.jabref' Java module

[...]

FAILURE: Build failed with an exception.

* Where:
Build file '/home/test/.cache/yay/jabref/src/jabref-5.15/build.gradle' line: 546

* What went wrong:
A problem occurred evaluating root project 'JabRef'.
> Could not get unknown property 'baseDir' for extension 'reporting' of type org.gradle.api.reporting.ReportingExtension.

gothicVI commented on 2025-01-18 22:49 (UTC)

@rellieberman: new version also applies the patch due to this PR: https://github.com/JabRef/jabref/pull/11544/files

rellieberman commented on 2025-01-18 22:16 (UTC)

Worked, Thank you!

Can you explain what went wrong?

Bevan commented on 2025-01-17 16:01 (UTC)

@rellieberman: I just pushed another change to avoid jitpack. Could you please try version 5.15-3?

rellieberman commented on 2025-01-16 23:01 (UTC)

This time I got a different error message - the same as reported by nbg.

  • What went wrong: A problem occurred configuring root project 'JabRef'.

    Could not resolve all artifacts for configuration 'classpath'. Could not resolve com.github.koppor.gradle-modules-plugin:gradle-modules-plugin:jitpack-SNAPSHOT. Required by: root project : > com.github.koppor:gradle-modules-plugin:jitpack-SNAPSHOT:33f60fd812-1 > Could not resolve com.github.koppor.gradle-modules-plugin:gradle-modules-plugin:jitpack-SNAPSHOT.

rellieberman commented on 2025-01-16 22:57 (UTC)

I've tried building yesterday and today with the same error. The line reads as follows: Using JDK from /usr/lib/jvm/java-21-openjdk to build JabRef.

Thanks!

Bevan commented on 2025-01-16 22:55 (UTC) (edited on 2025-01-17 15:58 (UTC) by Bevan)

@rellieberman: I cannot reproduce this issue. Spontaneously, I can imagine two possible reasons:

  • A temporary issue with your network or the mirror. Another build attempt should then work properly.

  • An incompatibility with your Java version. When building the package, there should be a line printed like "Using JDK from /usr/lib/jvm/java-21-openjdk to build JabRef." What exactly does it say in your case?