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.
System does not boot after update
Reported by yaroslav-pohil · filed Jan 8, 2026Closed upstream on 2026-01-08 by dhh, as a duplicate of #4137 (R-3973). GitHub close reason: duplicate.
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
i5-8350U, Intel UHD Graphics 620, Omarchy 3.3.0
What's wrong?
On Omarchy 3.3.0, if I start update, the system does not boot after reload.
Context
I have started update to 3.3.0 this morning, and after some time I saw an error while updating(sorry, don't have a screenshot). It prompted me to restart the system, which I did, and now I see Omarchy 3.3.0 with Hyperland errors:
<img width="1920" height="1080" alt="Image" src="https://github.com/user-attachments/assets/1d91c43a-d94a-4fed-98d6-b344f403a074" />
Then I decided that maybe I just need re-run update, but after doing it, system does not load - I enter my password, load bar goes 100% and nothing happens for like 1m, after that machine is auto-restarted. The workaround for me is to restore snapshot of the system before 2nd update was executed(where I see Hyperland errors).
I'm attaching logs from journalctl from system that does not boot.
stuck_on_boot.log
ChatGPT assumes there's mounting issue based on entries:
systemd-remount-fs.service: Main process exited, status=1/FAILURE
Failed to start Remount Root and Kernel File Systems.View raw text
### System details i5-8350U, Intel UHD Graphics 620, Omarchy 3.3.0 ### What's wrong? On Omarchy 3.3.0, if I start update, the system does not boot after reload. ### Context I have started update to 3.3.0 this morning, and after some time I saw an error while updating(sorry, don't have a screenshot). It prompted me to restart the system, which I did, and now I see Omarchy 3.3.0 with Hyperland errors: <img width="1920" height="1080" alt="Image" src="https://github.com/user-attachments/assets/1d91c43a-d94a-4fed-98d6-b344f403a074" /> Then I decided that maybe I just need re-run update, but after doing it, system does not load - I enter my password, load bar goes 100% and nothing happens for like 1m, after that machine is auto-restarted. The workaround for me is to restore snapshot of the system before 2nd update was executed(where I see Hyperland errors). I'm attaching logs from `journalctl` from system that does not boot. [stuck_on_boot.log](https://github.com/user-attachments/files/24492964/stuck_on_boot.log) ChatGPT assumes there's mounting issue based on entries: ``` systemd-remount-fs.service: Main process exited, status=1/FAILURE Failed to start Remount Root and Kernel File Systems. ```
- stuck_on_boot.log
- 1d91c43a-d94a-4fed-98d6-b344f403a074
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.