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

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

nbg commented on 2024-10-06 18:53 (UTC) (edited on 2024-10-06 18:55 (UTC) by nbg)

I cannot install jabref. I'm getting a similar error message by @rgarber11


FAILURE: Build failed with an exception.

* 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.
         > Could not get resource 'https://jitpack.io/com/github/koppor/gradle-modules-plugin/gradle-modules-plugin/jitpack-SNAPSHOT/gradle-modules-plugin-jitpack-33f60fd812-1.pom'.
            > Could not GET 'https://jitpack.io/com/github/koppor/gradle-modules-plugin/gradle-modules-plugin/jitpack-SNAPSHOT/gradle-modules-plugin-jitpack-33f60fd812-1.pom'.
               > Read timed out

rgarber11 commented on 2024-09-24 14:51 (UTC)

Yeah, the update just worked today. No idea what happened yesterday. Sorry about that!

Bevan commented on 2024-09-24 06:38 (UTC)

Strange. I cannot reproduce the issue with 5.15-2 anymore and did multiple successful builds now. Do you work in a clean build directory? Can others report if it works for them?

rgarber11 commented on 2024-09-23 21:42 (UTC) (edited on 2024-09-23 21:44 (UTC) by rgarber11)

5.15-2 returns the same error for me as rhysperry111. Doing some poking around, I found that the settings.gradle contains:

pluginManagement {
    resolutionStrategy {
        eachPlugin {
            // Hint from https://github.com/jitpack/jitpack.io/issues/1459#issuecomment-1279851731
            // Updated solution at https://github.com/foodiestudio/convention-plugins?tab=readme-ov-file#convention-plugins
            if (requested.id.id.startsWith("com.github.koppor")) {
                // This is https://github.com/java9-modularity/gradle-modules-plugin/pull/282
                useModule("com.github.koppor:gradle-modules-plugin:jitpack-SNAPSHOT")
            }
        }
    }
...

which I assume is at fault.

Bevan commented on 2024-09-23 20:00 (UTC)

Thanks rhysperry111 for the notice. I pushed version 5.15-2 which should fix this issue.

rhysperry111 commented on 2024-09-23 10:05 (UTC) (edited on 2024-09-23 10:21 (UTC) by rhysperry111)

I'm currently getting the following error on build:

FAILURE: Build failed with an exception.

* Where:
Build file '/home/rhys/.cache/paru/clone/jabref/src/jabref-5.15/build.gradle' line: 14

* What went wrong:
Plugin [id: 'com.github.koppor.gradle-modules-plugin', version: 'jitpack-SNAPSHOT', artifact: 'com.github.koppor:gradle-modules-plugin:jitpack-SNAPSHOT'] was not found in any of the following sources:

- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Included Builds (No included builds contain this plugin)
- Plugin Repositories (could not resolve plugin artifact 'com.github.koppor:gradle-modules-plugin:jitpack-SNAPSHOT')
  Searched in the following repositories:
    maven(https://jitpack.io)
    Gradle Central Plugin Repository

The -git version seems to work. Maybe upstream needs to make a release?

Nordwin commented on 2024-04-10 14:22 (UTC)

@Bevan: I do, thank you for pointing me towards that link. That fixes it for me

Bevan commented on 2024-04-05 21:37 (UTC)

@Nordwin: Do you have the environment variable $LD_LIBRARY_PATH set in a custom way? See https://bugs.archlinux.org/task/77183.

Nordwin commented on 2024-04-05 08:07 (UTC)

Even with jdk21-openjdk I cannot start jabref:

Error occurred during initialization of boot layer java.lang.UnsatisfiedLinkError: /usr/lib/jvm/java-21-openjdk/lib/libnio.so: /usr/lib/jvm/java-21-openjdk/lib/libnio.so: undefined symbol: reuseport_available

Rhinoceros commented on 2024-03-29 05:31 (UTC)

Thanks @Bevan. FWIW I tried building with the newer jdk 22, but it failed.