Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-2991GitHub issuePublicReceived

Chromium theming issue / Persistent accent color after theme change

Reported by erik-brueggemann · filed Sep 22, 2025Closed upstream on 2026-01-31 by its own reporter erik-brueggemann. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.

Received and recorded verbatim. Nothing has been checked yet.

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

Chromium theming issue / Persistent accent color after theme changerevision 1 · captured 2026-10-04 11:35 UTC via poll

System details

AMD Ryzen 9 9950X3D, AMD Radeon RX 9070 XT, Omarchy v3.0.1, Linux 6.16.8-arch2-1

What's wrong?

Problem Description

After the recent micro-fork of Chromium rolled out, some theming elements seem to be stuck (at least for me) on a previous accent color, even after switching themes. This issue affects both Chromium and also recently Brave.

When I switched from the Osaka Jade theme (active theme when I installed the update) to the Matte Black theme (my current theme), the primary browser window updated correctly. However, some menus and elements, such as the sidebar and context menu highlights, remain the old accent color (green, see below).

<img width="1714" height="150" alt="Image" src="https://github.com/user-attachments/assets/57c52a13-7728-40fa-aeac-f7416f801b66" />


<img width="1701" height="1390" alt="Image" src="https://github.com/user-attachments/assets/b9a29fde-6580-43ea-991a-8f6718f40b56" />


<img width="1701" height="1390" alt="Image" src="https://github.com/user-attachments/assets/c94649a2-9170-444b-8aa0-e9808ebe938f" />


The green accent persists despite multiple browser restarts and Omarchy version upgrades.

This also affects Brave Browser after the recent theming update, where the accent color is stuck on red for me - regardless of the selected Omarchy theme (e.g., Matte Black, Tokyo Night, Osaka Jade).

<img width="1714" height="173" alt="Image" src="https://github.com/user-attachments/assets/8e0b7ff2-1da1-46c6-bba0-15d34d09529c" />


<img width="1717" height="141" alt="Image" src="https://github.com/user-attachments/assets/3ee34342-0c12-468c-95af-701a3b7a6e2b" />


<img width="1714" height="194" alt="Image" src="https://github.com/user-attachments/assets/c53a9bfe-f380-4fdb-a3e1-3de56a7f536a" />


Additional Information

When I try to manually change the theme, the browser displays a message stating:

Theme is set by your Organization Your administrator has set a default theme which cannot be changed.
View raw text
### System details

AMD Ryzen 9 9950X3D, AMD Radeon RX 9070 XT, Omarchy v3.0.1,  Linux 6.16.8-arch2-1

### What's wrong?

## Problem Description

After the recent micro-fork of Chromium rolled out, some theming elements seem to be stuck (at least for me) on a previous accent color, even after switching themes. This issue affects both Chromium and also recently Brave.

When I switched from the Osaka Jade theme (active theme when I installed the update) to the Matte Black theme (my current theme), the primary browser window updated correctly. However, some menus and elements, such as the sidebar and context menu highlights, remain the old accent color (green, see below). 

<img width="1714" height="150" alt="Image" src="https://github.com/user-attachments/assets/57c52a13-7728-40fa-aeac-f7416f801b66" />

---

<img width="1701" height="1390" alt="Image" src="https://github.com/user-attachments/assets/b9a29fde-6580-43ea-991a-8f6718f40b56" />

---

<img width="1701" height="1390" alt="Image" src="https://github.com/user-attachments/assets/c94649a2-9170-444b-8aa0-e9808ebe938f" />

---

The green accent persists despite multiple browser restarts and Omarchy version upgrades.

This also affects Brave Browser after the recent theming update, where the accent color is stuck on red for me - regardless of the selected Omarchy theme (e.g., Matte Black, Tokyo Night, Osaka Jade).

<img width="1714" height="173" alt="Image" src="https://github.com/user-attachments/assets/8e0b7ff2-1da1-46c6-bba0-15d34d09529c" />

---

<img width="1717" height="141" alt="Image" src="https://github.com/user-attachments/assets/3ee34342-0c12-468c-95af-701a3b7a6e2b" />

---

<img width="1714" height="194" alt="Image" src="https://github.com/user-attachments/assets/c53a9bfe-f380-4fdb-a3e1-3de56a7f536a" />

---

## Additional Information

When I try to manually change the theme, the browser displays a message stating:

> **Theme is set by your Organization**
> Your administrator has set a default theme which cannot be changed.
  • 57c52a13-7728-40fa-aeac-f7416f801b66
  • b9a29fde-6580-43ea-991a-8f6718f40b56
  • c94649a2-9170-444b-8aa0-e9808ebe938f
  • 8e0b7ff2-1da1-46c6-bba0-15d34d09529c
  • 3ee34342-0c12-468c-95af-701a3b7a6e2b
  • c53a9bfe-f380-4fdb-a3e1-3de56a7f536a

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.