Libnotify: Segfault when querying notification server capabilities
Reported by a user, when trying to start Briar on a fresh installation of Raspbian (Raspberry Pi version of Debian). On the first glance doesn't look like a platform-specific issue: we could probably handle connection issues with "proxy" more gracefully?
10:09:01.865 [main] INFO org.briarproject.briar.desktop.Main - This is briar-desktop version 0.3.1-snapshot
10:09:01.888 [main] INFO org.briarproject.briar.desktop.Main - Build info:
10:09:01.892 [main] INFO org.briarproject.briar.desktop.Main - Git hash 93aaf03c7b364c3e82108f729ebd8b0aac8fd959-dirty
10:09:01.897 [main] INFO org.briarproject.briar.desktop.Main - Commit time 2023-01-15 15:32:21
10:09:01.902 [main] INFO org.briarproject.briar.desktop.Main - Branch build-for-arm64
(process:3319): libnotify-WARNING **: 10:09:21.347: Failed to connect to proxy
10:09:21.355 [AWT-EventQueue-0] INFO o.b.b.d.n.l.LibnotifyNotificationProvider - Notification server capabilities:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x0000000000000000, pid=3319, tid=3464
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.5+8 (17.0.5+8) (build 17.0.5+8)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.5+8 (17.0.5+8, mixed mode, tiered, compressed oops, compressed class ptrs, serial gc, linux-aarch64)
# Problematic frame:
# C 0x0000000000000000
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/<USER>/briar-desktop-arm64-0.3.1-snapshot/bin/hs_err_pid3319.log
#
# If you would like to submit a bug report, please visit:
# https://github.com/adoptium/adoptium-support/issues
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted