Arch Linux User Repository

@antti Yeah I just tested the appimage again to be completely certain and yeah it definitely also crashes with the exact same issue... welp I guess I'll wait for modrinth to fix the issue then... sorry for the trouble here then

If the appimage also crashes, it's a modrinth problem and not a packaging problem

No matter what version I install via yay (both this, the bin version, and the appimage), they all crash when I click into any non-custom modpacks that I have installed and outputs the following in the console:

/usr/bin/modrinth-app: line 8: 33027 Segmentation fault (core dumped) env MODRINTH_EXTERNAL_UPDATE_PROVIDER=1 /opt/modrinth-app/modrinth-app "$@"

When going into a custom modpack and clicking the 3 dots to either open folder or export the modpack, the app also crashes and gives the exact same error

(I'm running on a R9 5900X and a 4070 Ti Super)

@antti That was the only thing that got it to actually work on my machine. And now the strangest thing is that running the bin in /opt/modrinth-app also works now??? I'm just gonna force modrinth to run on integrated graphics, so I don't have to mess with this nvidia stuff again.

(The original __NV_DISABLE_EXPLICIT_SYNC=1 came from a lot of A/B testing with things people suggested in a github issue)

@lynx_xdg That is not working on my machine at least.

If you don't mind, could you add a patch to change /usr/bin/modrinth-app to this? The __NV_DISABLE_EXPLICIT_SYNC=1 actually fixes the issue WEBKIT_DISABLE_DMABUF_RENDERER=1 tried to fix.

#!/bin/sh

# Make the app work for nvidia users, but laggy
if lspci | grep -i nvidia > /dev/null; then
  #export WEBKIT_DISABLE_DMABUF_RENDERER=1
  export __NV_DISABLE_EXPLICIT_SYNC=1 
fi

env MODRINTH_EXTERNAL_UPDATE_PROVIDER=1 /opt/modrinth-app/modrinth-app "$@"

Anyone getting this error? /usr/bin/modrinth-app: line 8: 41528 Segmentation fault (core dumped) env MODRINTH_EXTERNAL_UPDATE_PROVIDER=1 /opt/modrinth-app/modrinth-app "$@"

sudo archlinux-java set java-17-openjdk worked for me. I had the same issue as @merlinity, except with it trying to use Java 8.

@merlinity Your system java default is 11. Run archlinux-java set java-17-openjdk or something. I honestly have no idea how one is supposed to properly do this in a PKGBUILD. I don't think calling archlinux-java in the PKGBUILD is the correct solution and I can't really hardcode anything in the PATH as there is no certainty which java distribution is used. I guess I could depend directly on jdk17-openjdk and do like export PATH="/usr/lib/jvm/java-17-openjdk/bin/:$PATH" but that doesn't seem correct either.

When I'm trying to install this package, I'm still getting an error.

Seems to be the same error dbb got:

  FAILURE: Build failed with an exception.

  * What went wrong:
  Gradle requires JVM 17 or later to run. Your build is currently configured to use JVM 11.

Is this a me problem or anyone else getting this too?

Here's the full error log:

error: theseus@0.10.20: Gradle build failed with exit status: 1
error: failed to run custom build command for `theseus v0.10.20 (/home/merlinity/.cache/yay/modrinth-app/src/code-0.10.20/packages/app-lib)`

Caused by:
  process didn't exit successfully: `/home/merlinity/.cache/yay/modrinth-app/src/code-0.10.20/apps/app/target/release/build/theseus-09e6411ab4faacdb/build-script-build` (exit status: 1)
  --- stdout
  cargo::rerun-if-changed=.env
  cargo::rerun-if-changed=java/gradle
  cargo::rerun-if-changed=java/src
  cargo::rerun-if-changed=java/build.gradle.kts
  cargo::rerun-if-changed=java/settings.gradle.kts
  cargo::rerun-if-changed=java/gradle.properties
  cargo::rustc-env=MODRINTH_URL=https://modrinth.com/
  cargo::rustc-env=MODRINTH_API_URL=https://api.modrinth.com/v2/
  cargo::rustc-env=MODRINTH_API_URL_V3=https://api.modrinth.com/v3/
  cargo::rustc-env=MODRINTH_SOCKET_URL=wss://api.modrinth.com/
  cargo::rustc-env=MODRINTH_LAUNCHER_META_URL=https://launcher-meta.modrinth.com/
  cargo::rustc-env=JAVA_JARS_DIR=/home/merlinity/.cache/yay/modrinth-app/src/code-0.10.20/apps/app/target/release/build/theseus-1eb6816d7bea45c5/out/java/libs
  Downloading https://services.gradle.org/distributions/gradle-9.1.0-bin.zip
  ............10%.............20%.............30%.............40%.............50%............60%.............70%.............80%.............90%.............100%

  Welcome to Gradle 9.1.0!

  Here are the highlights of this release:
   - Full Java 25 support
   - Native task graph visualization
   - Enhanced console output

  For more details see https://docs.gradle.org/9.1.0/release-notes.html

  To honour the JVM settings for this build a single-use Daemon process will be forked. For more on this, please refer to https://docs.gradle.org/9.1.0/userguide/gradle_daemon.html#sec:disabling_the_daemon in the Gradle documentation.
  cargo::error=Gradle build failed with exit status: 1

  --- stderr

  FAILURE: Build failed with an exception.

  * What went wrong:
  Gradle requires JVM 17 or later to run. Your build is currently configured to use JVM 11.

  * Try:
  > Run with --stacktrace option to get the stack trace.
  > Run with --info or --debug option to get more log output.
  > Run with --scan to generate a Build Scan (Powered by Develocity).
  > Get more help at https://help.gradle.org.
warning: build failed, waiting for other jobs to finish...
failed to build app: failed to build app
       Error failed to build app: failed to build app
/home/merlinity/.cache/yay/modrinth-app/src/code-0.10.20/apps/app:
 ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL  @modrinth/app@ tauri: `tauri "build" "--config" "tauri-release.conf.json" "--no-bundle"`
Exit status 1