fix(linux): Wayland Vulkan warning and Tailscale pairing/connect errors - #89
Merged
sambitcreate merged 1 commit intoSep 12, 2026
Conversation
…ailscale operator denial Disable Chromium Vulkan on Linux Wayland to suppress the Ozone incompatibility warning. Classify Tailscale TLS probe failures and resolve them from remote:beginPairing instead of rejecting IPC. Latch tailscale_permission_denied on connect so Settings can show the operator grant instead of an unhandled handler error. Co-authored-by: Sambit Biswas <sambitcreate@users.noreply.github.com>
sambitcreate
merged commit Sep 12, 2026
e0f4836
into
feature/linux-desktop-support
5 of 8 checks passed
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.
Fixes three Linux-branch issues:
--disable-features=Vulkanbefore the main module loads so Chromium does not log the Ozone Wayland Vulkan incompatibility warning. An explicit--ozone-platform=x11override is respected. Hardware acceleration stays enabled.remote:beginPairingresolves a structured{ ok: false, code, message }outcome for those cases instead of rejecting the IPC handler. No pairing session is created.remote:tailscaleConnectno longer rejects ontailscale_permission_denied. The settings snapshot latchestailscaleErrorCode: "permission_denied"with copy to runsudo tailscale set --operator=$USER. Disconnect/takeover still throw the typed code.Native iOS/Android clients are unchanged; this is desktop IPC and Linux Chromium flags only.