Arch Linux User Repository

@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.

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

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.

@MartinDiehl: Thanks for the comment! This error should now be fixed in version 5.15-5.

I can't build it at the moment. It seems that a dependency does not exist anymore

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileJava'.
> Could not resolve all files for configuration ':compileClasspath'.
   > Could not resolve com.github.sialcasa.mvvmFX:mvvmfx-validation:f195849ca9.
     Required by:
         root project 'JabRef'
      > Could not resolve com.github.sialcasa.mvvmFX:mvvmfx-validation:f195849ca9.
         > Could not get resource 'https://s01.oss.sonatype.org/content/repositories/snapshots/com/github/sialcasa/mvvmFX/mvvmfx-validation/f195849ca9/mvvmfx-validation-f195849ca9.pom'.
            > Could not GET 'https://s01.oss.sonatype.org/content/repositories/snapshots/com/github/sialcasa/mvvmFX/mvvmfx-validation/f195849ca9/mvvmfx-validation-f195849ca9.pom'. Received status code 504 from server: Gateway Time-out
> There is 1 more failure with an identical cause.

@PureFallen: Do I understand correctly that even with version 6.0-alpha.4 you observe this issue? In that case I think it should be re-reported as an issue upstream. I don't see any way to address this in this package. Or do I miss something?

It seems that JavaFX dropped support for GTK2 and uses GTK3 instead even when -Djdk.gtk.version=2 was specified. The error from @matteodelabre makes a return and also seems to affect uses of XWayland:

https://github.com/JabRef/jabref/issues/12377

The issue claims that JabRef 6.0 fixes that issue. However, I cannot reproduce that behavior and who knows how long 6.0 will be stuck in Pre-Release...

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

@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

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.

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

Worked, Thank you!

Can you explain what went wrong?