Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Steam appearance broken by theme hook (40-steam.sh reinstalls Adwaita-for-Steam on every theme change)
Reported by haripako · filed May 17, 2026Closed upstream on 2026-05-18 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
Summary
The 40-steam.sh theme hook reinstalls the Adwaita-for-Steam skin every time omarchy theme set runs (including during omarchy update migrations). This breaks Steam's appearance when:
- The active theme doesn't fully support the Adwaita-for-Steam color variables, or
- The user prefers Steam's default appearance without the skin
Steps to reproduce
- Have Steam installed via
omarchy install steam - Run
omarchy theme set <any theme>or runomarchy update(which may trigger theme migrations) - Open Steam → appearance is broken / skin is reapplied
Root cause
~/.config/omarchy/hooks/theme-set.d/40-steam.sh generates a steam.css from the active theme's color palette and runs install.py from Adwaita-for-Steam, which populates ~/.local/share/Steam/steamui/libraryroot.custom.css. If the theme doesn't export all expected color variables, the generated CSS is incomplete and Steam renders incorrectly.
Workaround
Option A — Disable the hook:
chmod -x ~/.config/omarchy/hooks/theme-set.d/40-steam.sh
cd ~/.local/share/steam-adwaita && python install.py --uninstallNote: omarchy update may restore execute permissions, causing the issue to recur.
Option B (more resilient) — Make the hook exit early:
Add exit 0 as the second line of 40-steam.sh so it runs but does nothing, even if permissions are restored by an update.
Suggested fix
- Guard the hook with a check for a user opt-in flag, e.g.
~/.config/omarchy/toggles/steam-theme, so it only applies the skin if the user has explicitly enabled it - Or add a
omarchy toggle steam-themecommand consistent with other toggles
Environment
- Omarchy 3.8.1
- Tested with Tokyo Night theme (and variants)
- Steam installed natively (not Flatpak/Snap)
View raw text
## Summary The `40-steam.sh` theme hook reinstalls the Adwaita-for-Steam skin every time `omarchy theme set` runs (including during `omarchy update` migrations). This breaks Steam's appearance when: - The active theme doesn't fully support the Adwaita-for-Steam color variables, or - The user prefers Steam's default appearance without the skin ## Steps to reproduce 1. Have Steam installed via `omarchy install steam` 2. Run `omarchy theme set <any theme>` or run `omarchy update` (which may trigger theme migrations) 3. Open Steam → appearance is broken / skin is reapplied ## Root cause `~/.config/omarchy/hooks/theme-set.d/40-steam.sh` generates a `steam.css` from the active theme's color palette and runs `install.py` from `Adwaita-for-Steam`, which populates `~/.local/share/Steam/steamui/libraryroot.custom.css`. If the theme doesn't export all expected color variables, the generated CSS is incomplete and Steam renders incorrectly. ## Workaround **Option A — Disable the hook:** ```bash chmod -x ~/.config/omarchy/hooks/theme-set.d/40-steam.sh cd ~/.local/share/steam-adwaita && python install.py --uninstall ``` Note: `omarchy update` may restore execute permissions, causing the issue to recur. **Option B (more resilient) — Make the hook exit early:** Add `exit 0` as the second line of `40-steam.sh` so it runs but does nothing, even if permissions are restored by an update. ## Suggested fix - Guard the hook with a check for a user opt-in flag, e.g. `~/.config/omarchy/toggles/steam-theme`, so it only applies the skin if the user has explicitly enabled it - Or add a `omarchy toggle steam-theme` command consistent with other toggles ## Environment - Omarchy 3.8.1 - Tested with Tokyo Night theme (and variants) - Steam installed natively (not Flatpak/Snap)
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.