BlueJ Flatpak on Asahi Linux (NixOS) crash

[RossComputerGuy]

F: Not sharing "/home/ross/.fonts" with sandbox: Path "/usr" is reserved by Flatpak
1月 11, 2024 8:06:21 午後 com.sun.javafx.application.PlatformImpl startup
警告: Unsupported JavaFX configuration: classes were loaded from 'unnamed module @27ead3ef'
glx: failed to create dri3 screen
failed to load driver: asahi

(java:6): Gdk-WARNING **: 20:06:22.226: XSetErrorHandler() called with a GDK error trap pushed. Don't do that.
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000fffdb17cc2a4, pid=6, tid=50
#
# JRE version: OpenJDK Runtime Environment 21.9 (17.0.9+7) (build 17.0.9+7)
# Java VM: OpenJDK 64-Bit Server VM 21.9 (17.0.9+7, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
# Problematic frame:
# C  [libjfxwebkit.so+0x280c2a4]
#
# Core dump will be written. Default location: Core dumps may be processed with "/nix/store/p92i9sdhn3011a79bq6wfqn8yjrfv57g-systemd/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /home/ross/core.6)
#
# An error report file with more information is saved as:
# /home/ross/hs_err_pid6.log
#
# If you would like to submit a bug report, please visit:
#   https://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
/app/bin/org.bluej.BlueJ: 7 行:     6 中止                  (コアダンプ) "$JAVAPATH/bin/java" -Djavafx.embed.singleThread=true -Dawt.useSystemAAFontSettings=on -cp "$CP:$JAVAFX_CP" bluej.Boot "$@"

BlueJ Flatpak version: 5.2.1

[neilccbrown]

Unfortunately, these crashes in Java itself are usually caused by a bug outside our control. That said, it may be worth uploading the first part of the HS log (/home/ross/hs_err_pid6.log) that has a full stack trace, to at least see when it went wrong.

[RossComputerGuy]

Sorry I haven't responded quicker, here's the error log.

hs_err_pid6.log

[neilccbrown]

It is a Java crash, which means it shouldn't happen and is not something we can directly fix... but having said that, the log shows it occurred while initialising the submitter extension. If you don't need to use this (if you don't know what it is, you don't need it) it may be worth finding "submitter.jar" in the extensions2 directory within the bluej installation and just deleting it. It won't have a negative effect but if you're lucky it may help avoid the crash.

[RossComputerGuy]

Where would submitter.jar be?

Edit: found it in /app/bluej/lib/extensions2/submitter.jar inside the Flatpak but it cannot be removed. The maintainer of the Flatpak will have to remove it.