ANSWERED Immediate Crash: X Connection to :0 broken

[voidfactory 0]

Hi,

after being able to install eddie-ui-git again on my CachyOS system, with Niri and DMS, the program starts, asks me for system permission and then initializes, only to immediately crash once it has finished initializing. Interestingly, it also immediately crashes Discord when it happens to be open. his is the entire process of what happens when I type eddie-ui into the terminal: 

❯ eddie-ui
Could not set X locale modifiers
Gtk not found (missing LD_LIBRARY_PATH to libgtk-x11-2.0.so.0?), using built-in colorscheme
. 2026-10-31 17:05:46.452 - Eddie version: 2.27.2 / linux_x64, System: Linux, Name: CachyOS Linux, Version: Linux XXXX 7.3.0-4-cachyos #1 SMP PREEMPT_DYNAMIC Fri, 23 Oct 2026 15:59:50 +0000 x86_64 GNU/Linux, Framework: 6.8.0.96 (tarball Wed Jan 15 10:20:48 UTC 2020); Framework: v4.0.30319
. 2026-10-31 17:05:46.468 - Command line arguments (1): path.resources="/usr/share/eddie-ui"
. 2026-10-31 17:05:46.709 - Raise system privileges
. 2026-10-31 17:05:46.710 - Elevated launch with method 'pkexec': /usr/lib/eddie-ui/eddie-cli-elevated
. 2026-10-31 17:05:49.893 - Privileged tools run from: install directory (secure, no staging)
. 2026-10-31 17:05:49.893 - Runtime directory: /var/lib/eddie-vpn/run/spot
. 2026-10-31 17:05:50.108 - Collect network information
. 2026-10-31 17:05:50.382 - Reading options from /home/XXXX/.config/eddie/default.profile
. 2026-10-31 17:05:50.789 - WireGuard - Version: 1.0.0
. 2026-10-31 17:05:50.789 - OpenVPN - Version: 2.7.8 - OpenSSL 3.6.5 29 Sep 2026, LZO 2.10 (/usr/bin/openvpn)
. 2026-10-31 17:05:50.789 - SSH - Version: OpenSSH_10.6p1, OpenSSL 3.6.5 29 Sep 2026 (/usr/bin/ssh)
I 2026-10-31 17:05:50.789 - SSL - Not available
. 2026-10-31 17:05:50.935 - systemd-resolved restarted via systemctl

(eddie-tray:33496): libayatana-appindicator-WARNING **: 17:05:51.241: libayatana-appindicator is deprecated. Please use libayatana-appindicator-glib in newly written code.
I 2026-10-31 17:05:52.024 - Ready
. 2026-10-31 17:05:52.528 - Collect information about AirVPN completed
X connection to :0 broken (explicit kill or server shutdown).


I see that this is a display issue of some kind, but I'd appreciate any kind of guidance on how to diagnose and deal with the problem further. To note: I have previously tried installing eddie-ui, eddie-cli, eddie-ui as an appimage as well as through the git clone process. This is the eddie-ui-git version. Are there any remnants from those installations trying to interfere?


Best
 

[voidfactory 0]

After more tinkering, I deleted the folder for eddie at default.profile and was able to start the app without crashing. It will even let me log-in and connect to a server using the Connect to a recommended server option on the start screen. However, it will immediately crash when I press Activate Network Lock, and the program will also immediately crash once I restart it. I need to delete the .config folder again for it to reset and then it does open and I can log-in and connect. What is happening here? Is this a permissions issue?

The terminal at the moment of crash outputs this:

    Native Crash Reporting
=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
/usr/bin/eddie-ui: line 3: 82413 Aborted                    (core dumped) ./eddie-ui --path.resources=/usr/share/eddie-ui "$@"

Edited ... by voidfactory

[Staff 10692]

Hello!

Discord crashing at the same moment is the key detail: the X server itself is going away, not only Eddie. Eddie's UI is an X11 (Mono WinForms) application, so on Niri it runs through xwayland-satellite, like Discord. "X connection to :0 broken (explicit kill or server shutdown)" is what every X11 client prints when that server disappears, and the Mono SIGSEGV in your second message is most likely Eddie dying after it lost its display. It is not a permissions issue: elevation through pkexec worked and the privileged part started correctly.

The trigger is consistent: activating Network Lock. Eddie keeps the Network Lock state in its profile folder and applies it again at the next start, so the same step runs at every launch until you delete ~/.config/eddie. You don't need to delete it: just make sure Network Lock is off before closing Eddie, and the next start will be clean.

Important: if Eddie crashes while Network Lock is active, the firewall rules stay in place by design (that's what prevents leaks), so you may have no connectivity afterwards. Start Eddie again and deactivate Network Lock, or check the rules with:
 

sudo nft list ruleset

To see which process actually crashes, please run this right after a crash and post the output:

coredumpctl list --since "10 min ago"
journalctl --user -b --since "10 min ago" | grep -i -E "xwayland|satellite"

If xwayland-satellite shows up there, the problem is on the compositor side. Niri users have reported random crashes with exactly this message, fixed by updating xwayland-satellite (the -git version) or, in some cases, by going back to an older Mesa release:
https://github.com/niri-wm/niri/issues/3199 
Please also tell us your xwayland-satellite and Mesa versions. If you can, a quick test in a session with standard Xwayland (Plasma or GNOME) would confirm it: if Network Lock works there, Eddie's firewall part is fine.

About leftovers: the different Eddie builds share only the profile folder ~/.config/eddie, and the AppImage is self-contained. Just check that a single Eddie package is installed:

pacman -Qs eddie

In the meantime, two options that do not need X at all, both with Network Lock:
- Eddie CLI edition (eddie-cli)
- AirVPN Suite (Bluetit daemon and Goldcrest client): https://airvpn.org/linux/suite/

Kind regards
 

[voidfactory 0]

Fascinating! I've put the results of the command into a text file, as it is very long. The relevant part should be at the bottom since I queried right after clicking on the Network Lock option. 

Before doing all that, I did install and replace the xwayland-satellite version on the system with the -git version via yay. It is xwayland-satellite-git 0.8.3.r14.g7bf5e0d-1 

I've also reinstalled the latest Mesa drivers, but they were already installed. Querying pacman -Qs gives me this list: 

local/glu 9.0.3-3.1
    Mesa OpenGL utility library
local/lib32-mesa 3:26.2.4-1
    Open-source OpenGL drivers - 32-bit
local/lib32-opencl-mesa 3:26.2.4-1
    Open-source OpenCL drivers - 32-bit
local/lib32-vulkan-mesa-implicit-layers 3:26.2.4-1
    Mesa's implicit Vulkan layers - 32-bit
local/mesa 3:26.2.4-1
    Open-source OpenGL drivers
local/mesa-utils 9.0.0-7.1
    Essential Mesa utilities
local/opencl-mesa 3:26.2.4-1
    Open-source OpenCL drivers
local/vulkan-mesa-implicit-layers 3:26.2.4-1
    Mesa's implicit Vulkan layers

glxinfo | grep Mesa gives me the following

client glx vendor string: Mesa Project and SGI
OpenGL core profile version string: 4.6 (Core Profile) Mesa 26.2.4-arch3.1
OpenGL version string: 4.6 (Compatibility Profile) Mesa 26.2.4-arch3.1
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 26.2.4-arch3.1

There is only one version of eddie-ui installed, which is the -git version.

Since these seem to also affect OpenGL, I've also experiencing video playback issues for these last three weeks on certain streaming sites (Viki, WeTV). Could these issues actually be related? Or am I way off base there? It affects every browser, and even happens on my EndeavorOS Laptop, also using Niri and DUX Shell. Disregard if unrelated.

Best
 

erroroutput.txt

Edited ... by voidfactory

[Staff 10692]

@voidfactory

Thank you, the log you attached is exactly what was needed, and it shows the cause precisely.

First, a quick picture of the pieces involved. niri is your Wayland compositor which draws and manages every window on your desktop. Eddie UI (like Discord) is an X11 application, and niri does not talk X11 itself: X11 applications run through xwayland-satellite, a bridge that starts Xwayland, acts as the X11 window manager towards those applications and presents each X11 window to niri as a normal Wayland window. All your X11 applications share that single bridge and its single connection to niri.

When you activate Network Lock, Eddie opens a small dialog window. That window declares a minimum height of -5 pixels in its X11 size hints (WM_NORMAL_HINTS: min_size 102x-5). xwayland-satellite passes this value unchanged to the compositor as the Wayland minimum size, and the Wayland protocol (xdg_toplevel.set_min_size) forbids negative values: niri answers with a protocol error, the connection is closed and xwayland-satellite panics in the same second:
 

Quote

thread 'main' panicked at src/server/mod.rs:802:21: Failed flushing clientside events: Protocol(
xwayland-satellite exited with: exit status: 101

Since every X11 application goes through that same bridge, all of them lose their display at that moment, which is why Discord goes down too, and eddie-tray then segfaults (the core dump you found) as a consequence. niri itself keeps running and quietly restarts xwayland-satellite, without telling anyone that it has just crashed: no notification, no warning, just a fresh bridge where the old one used to be, in the best tradition of a strict code of silence.

The only visible symptom is your X11 applications vanishing all at once, and nobody saw anything. In other words, a single window asking to be at least minus five pixels tall is enough to take down every X11 application on your desktop: quite a lot of power for a negative number. So this is neither a permissions problem nor the Mesa issue we mentioned earlier, which is why updating xwayland-satellite did not help.

Two things are wrong here: the negative value in that Eddie dialog, which we will report to the Eddie developers, and xwayland-satellite crashing on it instead of ignoring or clamping it. A regular Xwayland or X11 session tolerates such a hint, which is why the problem appears only under xwayland-satellite. If you like, you can report it to the xwayland-satellite project with the lines above: https://github.com/Supreeeme/xwayland-satellite/issues

Until one of the two is fixed, on niri please use one of the options that do not need X at all, both with Network Lock:
- Eddie CLI edition (eddie-cli)
- AirVPN Suite (Bluetit daemon and Goldcrest client): https://airvpn.org/linux/suite/ 

About video playback on Viki and WeTV: it is not related to this crash. If it happens only while connected to the VPN, please try a few different servers and let us know.

Kind regards