Proof Portal

Sign in
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-4668GitHub issuePublicReceived

Zed theme sync still broken on Quattro: omazed package in [omarchy] repo predates the upstream fix

Reported by jardahrazdera · filed Aug 24, 2026Closed upstream on 2026-08-24 by its own reporter jardahrazdera, as not planned. Closed by its own reporter — not by itself evidence of a fix.

Open at source
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

Zed theme sync still broken on Quattro: omazed package in [omarchy] repo predates the upstream fixrevision 1 · captured 2026-10-04 12:03 UTC via poll

System details

Lenovo ThinkPad T14 Gen 6 (Intel Lunar Lake), Omarchy 4.0.0.alpha, omazed 2.0.1-1 from the [omarchy] repo

What's wrong?

Zed theme sync is still broken on a fresh Quattro install. This is the same bug as #7325, which was closed as fixed, but the fix never reached the package that Omarchy actually installs.

The problem is packaging, not code. Upstream aps6/omazed fixed this in commit 302cd39 ("feat: add unified Omarchy v4 (Quattro) support", 2026-08-15). But the omazed package in the [omarchy] repo is version 2.0.1-1, built on 2026-05-30 — about two and a half months before that fix. So it still contains the old Omarchy 3 paths.

In #7325 the advice was "reinstall omazed via the omarchy AUR install menu". That works if you build from the AUR, but omarchy-install-editor-zed runs omarchy-pkg-add zed omazed, which pulls the binary package from [omarchy]. That package is stale, so anyone installing Zed the normal way still gets the broken version.

Steps to reproduce

  1. Fresh Omarchy 4 install
  2. Menu > Install > Editor > Zed
  3. Change the system theme
  4. Zed does not follow

What the log shows (~/.local/share/omazed/sync.log)

[INFO] Setting Zed theme for: Last Horizon
[WARN] colors.toml not found: /home/jarek/.config/omarchy/current/theme/colors.toml
[WARN] Alacritty config not found: /home/jarek/.config/omarchy/current/theme/alacritty.toml
[INFO] Could not generate theme, skipping update

Both files exist, just under ~/.local/state/omarchy/current/theme/ since Quattro moved runtime state out of ~/.config.

Quick check that the shipped package is the old code

$ pacman -Qi omazed | grep -E 'Version|Build Date'
Version         : 2.0.1-1
Build Date      : Sat 30 May 2026 07:03:30 AM CEST

$ grep -c "local/state" /usr/bin/omazed
0

Upstream master has that path in two places; the shipped binary has none.

Besides the theme path, the old version also gets two other things wrong on Quattro, both fixed in the same upstream commit:

  • Light mode is detected from a light.mode marker file. Quattro dropped it and uses mode = "light" in colors.toml, so all light themes render dark in Zed.
  • omazed-generator.sh only reads color0..color15 keys. Quattro's colors.toml uses semantic names (red, bright_red, muted, ...), so every ANSI slot falls back to hardcoded defaults like #ff4444. The theme generates, it just does not match the palette.

I verified upstream master end to end on this machine and it works correctly: right palette, and light themes come out light.

Suggested fix

Rebuild the omazed package in the [omarchy] repo from current upstream master. Upstream's newest git tag is v1.1.1, so there is no 2.0.2 tag to build from yet -- it may need a release tag from aps6/omazed first, or a build pinned to 302cd39.

View raw text
### System details

Lenovo ThinkPad T14 Gen 6 (Intel Lunar Lake), Omarchy 4.0.0.alpha, omazed 2.0.1-1 from the `[omarchy]` repo

### What's wrong?

Zed theme sync is still broken on a fresh Quattro install. This is the same bug as #7325, which was closed as fixed, but the fix never reached the package that Omarchy actually installs.

The problem is packaging, not code. Upstream `aps6/omazed` fixed this in commit `302cd39` ("feat: add unified Omarchy v4 (Quattro) support", 2026-08-15). But the `omazed` package in the `[omarchy]` repo is version `2.0.1-1`, built on **2026-05-30** — about two and a half months before that fix. So it still contains the old Omarchy 3 paths.

In #7325 the advice was "reinstall omazed via the omarchy AUR install menu". That works if you build from the AUR, but `omarchy-install-editor-zed` runs `omarchy-pkg-add zed omazed`, which pulls the binary package from `[omarchy]`. That package is stale, so anyone installing Zed the normal way still gets the broken version.

**Steps to reproduce**

1. Fresh Omarchy 4 install
2. Menu > Install > Editor > Zed
3. Change the system theme
4. Zed does not follow

**What the log shows** (`~/.local/share/omazed/sync.log`)

```
[INFO] Setting Zed theme for: Last Horizon
[WARN] colors.toml not found: /home/jarek/.config/omarchy/current/theme/colors.toml
[WARN] Alacritty config not found: /home/jarek/.config/omarchy/current/theme/alacritty.toml
[INFO] Could not generate theme, skipping update
```

Both files exist, just under `~/.local/state/omarchy/current/theme/` since Quattro moved runtime state out of `~/.config`.

**Quick check that the shipped package is the old code**

```
$ pacman -Qi omazed | grep -E 'Version|Build Date'
Version         : 2.0.1-1
Build Date      : Sat 30 May 2026 07:03:30 AM CEST

$ grep -c "local/state" /usr/bin/omazed
0
```

Upstream master has that path in two places; the shipped binary has none.

Besides the theme path, the old version also gets two other things wrong on Quattro, both fixed in the same upstream commit:

- Light mode is detected from a `light.mode` marker file. Quattro dropped it and uses `mode = "light"` in `colors.toml`, so all light themes render dark in Zed.
- `omazed-generator.sh` only reads `color0`..`color15` keys. Quattro's `colors.toml` uses semantic names (`red`, `bright_red`, `muted`, ...), so every ANSI slot falls back to hardcoded defaults like `#ff4444`. The theme generates, it just does not match the palette.

I verified upstream master end to end on this machine and it works correctly: right palette, and light themes come out light.

### Suggested fix

Rebuild the `omazed` package in the `[omarchy]` repo from current upstream master. Upstream's newest git tag is `v1.1.1`, so there is no `2.0.2` tag to build from yet -- it may need a release tag from `aps6/omazed` first, or a build pinned to `302cd39`.

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.