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.
BrowserColorScheme "device" is rejected by Chromium-family browsers
Reported by timolehto · filed Sep 3, 2026 · open at source
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?
- AreaOutside the audited area· Decided by agents · verified
- 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?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
System details
Omarchy 4.0.2 with Chromium 151.0.7922.173 and Google Chrome 152.0.7977.75.
What happens
Omarchy writes this policy to each installed Chromium-family browser:
{"BrowserThemeColor":"#1a1b26","BrowserColorScheme":"device"}For example, it is written to /etc/chromium/policies/managed/color.json and /etc/opt/chrome/policies/managed/color.json.
Both chromium://policy and chrome://policy report BrowserColorScheme with status Error. BrowserThemeColor remains OK. The same shared writer also targets Brave and Edge, so they are likely affected too.
device is not an accepted value for this policy. Chromium's supported color-scheme choices are system, light, and dark; system preserves Omarchy's intended behavior of following the desktop light/dark appearance.
Expected behavior
Generated Chromium-family policy files use:
"BrowserColorScheme": "system"Existing installations should be migrated so the error disappears without requiring a user to change themes manually.
Related reports
This is distinct from the intentional managed-browser banner discussed in #5650 and #1817: the issue here is that the active policy itself is invalid.
View raw text
## System details
Omarchy 4.0.2 with Chromium 151.0.7922.173 and Google Chrome 152.0.7977.75.
## What happens
Omarchy writes this policy to each installed Chromium-family browser:
```json
{"BrowserThemeColor":"#1a1b26","BrowserColorScheme":"device"}
```
For example, it is written to `/etc/chromium/policies/managed/color.json` and `/etc/opt/chrome/policies/managed/color.json`.
Both `chromium://policy` and `chrome://policy` report `BrowserColorScheme` with status **Error**. `BrowserThemeColor` remains **OK**. The same shared writer also targets Brave and Edge, so they are likely affected too.
`device` is not an accepted value for this policy. Chromium's supported color-scheme choices are `system`, `light`, and `dark`; `system` preserves Omarchy's intended behavior of following the desktop light/dark appearance.
## Expected behavior
Generated Chromium-family policy files use:
```json
"BrowserColorScheme": "system"
```
Existing installations should be migrated so the error disappears without requiring a user to change themes manually.
## Related reports
This is distinct from the intentional managed-browser banner discussed in #5650 and #1817: the issue here is that the active policy itself is invalid.
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.
- Out of scopeDecided by agents · verified · 2026-10-09 10:43 UTC