From dd22059cedbf41c56c1cee635122d5f6d1f1c3d1 Mon Sep 17 00:00:00 2001 From: Arun Babu Neelicattu Date: Sun, 14 Jun 2026 19:35:54 +0200 Subject: [PATCH] flatpak: expose X11 socket unconditionally to allow clipboard fallback On Wayland hosts, Tauri's clipboard manager (via the 'arboard' crate) attempts to initialize its Wayland backend. However, it relies on the Wayland data-control protocols (ext-data-control-v1 or wlr-data-control-unstable-v1), which are not supported by the GNOME compositor (Mutter). When native Wayland clipboard initialization fails, 'arboard' attempts to fall back to X11 (XWayland). With '--socket=fallback-x11', Flatpak completely hides the X11 socket since a Wayland display was available on the host, causing the fallback to fail and disabling the clipboard entirely. Exposing the X11 socket unconditionally via '--socket=x11' ensures that the XWayland display is always accessible in the sandbox, allowing the clipboard copy operations to succeed. --- ai.lemonade_server.Lemonade/ai.lemonade_server.Lemonade.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/ai.lemonade_server.Lemonade/ai.lemonade_server.Lemonade.yaml b/ai.lemonade_server.Lemonade/ai.lemonade_server.Lemonade.yaml index e28d504..e06a2c8 100644 --- a/ai.lemonade_server.Lemonade/ai.lemonade_server.Lemonade.yaml +++ b/ai.lemonade_server.Lemonade/ai.lemonade_server.Lemonade.yaml @@ -12,7 +12,9 @@ finish-args: - --share=ipc - --share=network - --socket=wayland - - --socket=fallback-x11 + # we use x11 instead of fallback-x11; tauri/arboard requires Wayland data-control protocols + # mutter does not support these protocols yet + - --socket=x11 - --socket=pulseaudio # --device=dri can't expose /dev/accel/accel0, /dev/kfd (Flatpak < 1.8) - --device=all