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.
Walker shows duplicate Google Chrome entries
Reported by 3x3cut0r · filed Feb 23, 2026Closed upstream on 2026-02-24 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
System details
Omarchy 3.3.3
What's wrong?
I get duplicate "Google Chrome" entries in Omarchy launcher.
System has:
- /usr/share/applications/google-chrome.desktop
- /usr/share/applications/com.google.Chrome.desktop (NoDisplay=true)
Expected one visible entry, actual two.
Likely in Walker/Elephant desktopapplications provider path.
I opened an upstream issue with full repro details: https://github.com/abenz1267/elephant/issues/202
View raw text
### System details Omarchy 3.3.3 ### What's wrong? I get duplicate "Google Chrome" entries in Omarchy launcher. System has: - /usr/share/applications/google-chrome.desktop - /usr/share/applications/com.google.Chrome.desktop (NoDisplay=true) Expected one visible entry, actual two. Likely in Walker/Elephant desktopapplications provider path. I opened an upstream issue with full repro details: https://github.com/abenz1267/elephant/issues/202
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.