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.
openai-codex-desktop 26.924.22138-1 can't open existing conversations (regression from 26.915.31945-1)
Reported by gogetwoo · filed Sep 28, 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.4-1, kernel 7.2.5-3-omarchy, Hyprland (Wayland).
Package: openai-codex-desktop 26.924.22138-1 from the omarchy repo (previous: 26.915.31945-1).
What's wrong?
After omarchy update moved openai-codex-desktop from 26.915.31945-1 to 26.924.22138-1, the ChatGPT/Codex desktop app can no longer open any existing conversation. It shows an endless spinner and messages just queue. New conversations work normally.
Verified bug, not a local state problem:
- Reproduced twice, the second time after a clean pacman -U reinstall with the app fully closed.
- Downgrading to the cached 26.915.31945-1 fixes it immediately; re-upgrading breaks it again.
- The app's renderer enters resumeState=resuming but never sends thread/resume to its bundled app-server (codex-cli 0.158.0-alpha.2.1), which only ever receives thread/read and answers in ~2 ms. Local state DBs pass integrity checks.
This looks like an upstream regression in the app itself. Upstream tracking issue: https://github.com/openai/codex/issues/48419 (duplicates: #48413, #48397, #48345; suspected root cause in #48618, a SIGCHLD handler being overwritten at startup). Filing here so the package can be held back or flagged until a fixed version ships.
Workaround: sudo pacman -U /var/cache/pacman/pkg/openai-codex-desktop-26.915.31945-1-x86_64.pkg.tar.zst and add IgnorePkg = openai-codex-desktop to /etc/pacman.conf.
View raw text
### System details Omarchy 4.0.4-1, kernel 7.2.5-3-omarchy, Hyprland (Wayland). Package: `openai-codex-desktop` 26.924.22138-1 from the `omarchy` repo (previous: 26.915.31945-1). ### What's wrong? After `omarchy update` moved `openai-codex-desktop` from 26.915.31945-1 to 26.924.22138-1, the ChatGPT/Codex desktop app can no longer open any existing conversation. It shows an endless spinner and messages just queue. New conversations work normally. Verified bug, not a local state problem: - Reproduced twice, the second time after a clean `pacman -U` reinstall with the app fully closed. - Downgrading to the cached 26.915.31945-1 fixes it immediately; re-upgrading breaks it again. - The app's renderer enters `resumeState=resuming` but never sends `thread/resume` to its bundled app-server (`codex-cli 0.158.0-alpha.2.1`), which only ever receives `thread/read` and answers in ~2 ms. Local state DBs pass integrity checks. This looks like an upstream regression in the app itself. Upstream tracking issue: https://github.com/openai/codex/issues/48419 (duplicates: #48413, #48397, #48345; suspected root cause in #48618, a SIGCHLD handler being overwritten at startup). Filing here so the package can be held back or flagged until a fixed version ships. Workaround: `sudo pacman -U /var/cache/pacman/pkg/openai-codex-desktop-26.915.31945-1-x86_64.pkg.tar.zst` and add `IgnorePkg = openai-codex-desktop` to `/etc/pacman.conf`.
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 20:04 UTC