flatpak: expose X11 socket unconditionally to allow clipboard fallback#27
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.