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.
Install script fails due to package mirror 404 error and lacks dependency error handling
Reported by death366 · filed Mar 20, 2026Closed upstream on 2026-09-27 by its own reporter death366. GitHub close reason: completed. Closed by its own reporter — not by itself 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
AMD 70700X Nvidia RTX 4060 gaming oc
What's wrong?
While running the Omarchy OS installation/setup script, the process fails. The initial system upgrade attempts to download packages (including perl and git), but encounters a 404 Not Found error from stable-mirror.omarchy.org for the perl package.
Because the pacman transaction fails, git is never installed. However, the script does not catch this transaction failure and continues execution. It immediately attempts to clone the Omarchy repository, which throws a git: command not found error, followed by subsequent cd and execution errors since the repository was never cloned.
the log:
:: Retrieving packages...
perl-5.42.1-1-x86_64.pkg.tar.zst failed to download
error: failed retrieving file 'perl-5.42.1-1-x86_64.pkg.tar.zst' from stable-mirror.omarchy.org : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.
Cloning Omarchy from: https://github.com/basecamp/omarchy.git
bash: line 42: git: command not found
Using branch: master
bash: line 45: cd: /home/death/.local/share/omarchy: No such file or directory
bash: line 46: git: command not found
bash: line 47: cd: OLDPWD not set
Installation starting...
bash: line 58: /home/death/.local/share/omarchy/install.sh: No such file or directory
View raw text
### System details AMD 70700X Nvidia RTX 4060 gaming oc ### What's wrong? While running the Omarchy OS installation/setup script, the process fails. The initial system upgrade attempts to download packages (including perl and git), but encounters a 404 Not Found error from stable-mirror.omarchy.org for the perl package. Because the pacman transaction fails, git is never installed. However, the script does not catch this transaction failure and continues execution. It immediately attempts to clone the Omarchy repository, which throws a git: command not found error, followed by subsequent cd and execution errors since the repository was never cloned. the log: :: Retrieving packages... perl-5.42.1-1-x86_64.pkg.tar.zst failed to download error: failed retrieving file 'perl-5.42.1-1-x86_64.pkg.tar.zst' from stable-mirror.omarchy.org : The requested URL returned error: 404 warning: failed to retrieve some files error: failed to commit transaction (failed to retrieve some files) Errors occurred, no packages were upgraded. Cloning Omarchy from: https://github.com/basecamp/omarchy.git bash: line 42: git: command not found Using branch: master bash: line 45: cd: /home/death/.local/share/omarchy: No such file or directory bash: line 46: git: command not found bash: line 47: cd: OLDPWD not set Installation starting... bash: line 58: /home/death/.local/share/omarchy/install.sh: No such file or directory 
- Image
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.