fix(desktop): avoid Hyprland 0.48–0.50 Wayland color-manager startup crashes

[krankos]

Launching T3 Code on Hyprland/native Wayland can terminate immediately after creating its window with Custom primaries aren't supported. The same failure reproduces in a plain BrowserWindow using the release's Electron 44.4.5 / Chromium 152.0.7977.130 runtime, without loading T3 Code.

Root cause: Hyprland 0.48.0 added wp-color-manager-v1 (hyprwm/Hyprland#9444) and advertises FEATURE_SET_PRIMARIES, but rejects set_primaries outside debug mode. Chromium treats that as a fatal protocol error. Hyprland 0.51.0 accepts custom primaries (hyprwm/Hyprland#11499).

Fix: before Electron readiness, disable WaylandWpColorManagerV1 only when all of these hold:

• the resolved Ozone backend is wayland (Electron resolves it before app code runs) and the session is Hyprland;
• the user has not explicitly enabled or disabled the feature;
• hyprctl version -j reports a stock affected release (0.48.0, 0.48.1, 0.49.0, 0.50.0 or 0.50.1): version, v<version> tag and the upstream release commit all match, and the build is not dirty. Matching the commit keeps development builds that still report an old version/tag (e.g. Nix synthesizes v${VERSION}) on the default.

Everything else keeps color management enabled, including 0.51.0+, unknown versions, and any probe failure (hyprctl missing, timeout, bad JSON). The probe runs hyprctl without a shell, with a 1 s timeout and 64 KiB output cap. Existing disabled features are preserved and duplicates avoided. Native Wayland stays enabled.

Reproduction environment:

• EndeavourOS (Arch-based), x86_64; kernel 6.13.8-arch1-1.
• Hyprland package 0.48.1-4 (commit 29e2e59), native Wayland; Mesa 25.0.3-1.
• Hybrid graphics: Intel UHD Graphics 630 (i915) and NVIDIA GeForce GTX 1650 Mobile / Max-Q (nouveau).
• Initially observed on T3 Code 0.0.45-nightly.20261001.2525; isolated runtime reproduction also confirmed with 0.0.46-nightly.20261011.2994's Electron 44.4.5 / Chromium 152.0.7977.130.

Validation:

• vp test run src/app/DesktopEarlyElectronStartup.test.ts src/app/DesktopPreReadyPlatform.test.ts from apps/desktop: 48 tests passed. Covers all five affected releases, 0.51.0+, Nix-style dev builds with a stale tag, dirty builds, malformed/missing hyprctl output, session detection, stale Hyprland variables in other sessions, X11, feature-list merging, and explicit overrides.
• Lint and formatting on the four changed files and desktop tsc-rs --noEmit passed (Node 24).
• Release tag → commit hashes verified with git ls-remote --tags and the GitHub API.
• On the affected machine, an isolated Electron runtime with a minimal BrowserWindow reproduced the unmodified failure (exit 133). Loading the resolver bundled from this patch and applying its result before readiness opened the window and exited cleanly (exit 0), with automatic platform selection (wayland) and with an existing --disable-features=Vulkan (merged to Vulkan,WaylandWpColorManagerV1). A full packaged desktop rebuild was not run.

Implemented by Claude Opus 5.5 through Claude Code (claude-sd); reviewed by GPT-6 through Codex; final runtime check and update by Claude Code.

🤖 Generated with Claude Code

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR changes Linux desktop startup behavior by automatically disabling Chromium color management for selected Hyprland releases when no explicit feature override exists. Although the detection is narrowly scoped and tested, it changes a product default on an existing customer path and merits human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Path: .coderabbit.config.ts
• Review profile: CHILL
• Plan: Advanced
• Run ID: 72e1ca17-af95-489d-8c31-0c30d3e8c47e

---

📥 Commits

Reviewing files that changed from the base of the PR and between f7a41c9 and e0ef719.

---

📒 Files selected for processing (4)

• apps/desktop/src/app/DesktopEarlyElectronStartup.test.ts
• apps/desktop/src/app/DesktopEarlyElectronStartup.ts
• apps/desktop/src/app/DesktopPreReadyPlatform.test.ts
• apps/desktop/src/app/DesktopPreReadyPlatform.ts

---

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

---

📝 Walkthrough

📝 Walkthrough

Walkthrough

Linux startup checks the Ozone platform, Hyprland session, feature lists, and Hyprland build metadata. For specified stock builds on Wayland, startup adds WaylandWpColorManagerV1 to Chromium’s disable-features switch unless either feature list already specifies it.

Changes

Linux feature switch

Layer / File(s)	Summary
Resolve the feature switch apps/desktop/src/app/DesktopEarlyElectronStartup.ts, apps/desktop/src/app/DesktopEarlyElectronStartup.test.ts	The resolver parses feature lists and Hyprland version JSON. It returns an updated disable list only for specified clean stock builds when the session uses Wayland, Hyprland is detected, and neither feature list names the feature. Tests cover matching conditions and cases where the resolver returns null.
Apply the resolved switch apps/desktop/src/app/DesktopPreReadyPlatform.ts, apps/desktop/src/app/DesktopPreReadyPlatform.test.ts	Linux pre-ready setup runs hyprctl version -j with a one-second timeout and a 64 KiB output limit. It appends the resolver’s value when non-null. Tests cover an affected Wayland build, a later build, and an X11-resolved session.

Priority: ➖ Normal

Estimated code review effort: 3 (Moderate) | ~20 minutes

Change: Bug fix

Sequence Diagram(s)

sequenceDiagram
  participant DesktopPreReadyPlatform
  participant resolveLinuxDisableFeaturesSwitch
  participant hyprctl
  DesktopPreReadyPlatform->>resolveLinuxDisableFeaturesSwitch: pass platform, session, and feature lists
  resolveLinuxDisableFeaturesSwitch->>hyprctl: read version JSON when eligible
  hyprctl-->>resolveLinuxDisableFeaturesSwitch: return version and build metadata
  resolveLinuxDisableFeaturesSwitch-->>DesktopPreReadyPlatform: return updated disable-features value or null

Loading

Suggested reviewers: juliusmarminge

---

Merge Risk: ⚪ Minimal · up to e0ef7

No confirmed issue blocks merging. Coverage of the named Hyprland releases remains unverified.

Security Architecture Review

Security architecture risk: 🔵 Low · up to e0ef7

The workaround preserves existing feature controls and does not explicitly increase privileges. Its scope is narrow, but packaged executable provenance and failure behavior have not been fully verified.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

• inferred — The new executable boundary is reached during Linux Wayland startup when desktop names identify Hyprland and no feature override exists. A substituted executable would inherit the application's execution context, without an explicit privilege increase. No remotely controlled path to executable selection was established; packaged launcher environment trust remains unverified.

Trust Boundaries and Controls

• observed — Fixed execFileSync arguments avoid shell-command construction from metadata. Typed decoding and exact release matching restrict feature changes, while existing feature controls remain authoritative. These checks validate compatibility metadata; they do not authenticate the PATH-resolved executable.

Resilience and Maintainability Implications

• inferred — The synchronous transition limits asynchronous interleaving, and probe exceptions do not partially overwrite feature controls. Earlier desktop-entry and identity mutations predate the PR. No newly insecure persisted recovery state was established, but child cleanup after interruption and repeated construction remain runtime-evidence gaps.

Hardening Proposals

• proposed — Validate executable provenance and inherited environment in supported packaged launchers, and confirm timeout/interruption behavior before treating the subprocess as a guaranteed bounded startup dependency. These are assurance proposals, not verified vulnerabilities.

---

Pre-merge checks | 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Title check		The title clearly and concisely describes the primary fix: preventing Hyprland 0.48–0.50 Wayland color-manager startup crashes.
Description check		The description clearly covers the problem, root cause, implementation conditions, scope, verification results, limitations, and tool-assisted development. It does not include an explicit issue or mai…

---

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

---

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}