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.
ARM update reboot loop
Reported by FrikkinBatz · filed Sep 17, 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
aarch64 with asahi
What's wrong?
ARM update repeatedly requests a Hyprland reboot
Summary
On an aarch64/Asahi installation, omarchy update repeatedly requests a
reboot because Hyprland was updated, although the Omarchy-pinned package
versions have not changed. The system update indicator remains present after
the update.
Environment
- Omarchy:
4.0.2-2 - Architecture:
aarch64(Asahi) - Kernel:
linux-asahi 7.1.13.asahi3-1 - Hyprland:
0.56.2-3 - hyprland-guiutils:
0.2.2-3 - Installed hyprtoolkit:
0.5.4-5.1
Steps to reproduce
- On an aarch64 Omarchy installation, ensure the regular
extrarepository
provides a newer hyprtoolkit than the omarchy repository.
2. Run omarchy update.
3. Complete the update prompts.
Actual behavior
The updater explicitly targets these packages from the Omarchy repository:
omarchy/hyprland
omarchy/hyprtoolkit
omarchy/hyprland-guiutilsAt the time of testing:
extra/hyprtoolkit: 0.5.4-6
omarchy/hyprtoolkit: 0.5.4-5.1
installed: 0.5.4-5.1pacman -Qu therefore continues to report:
hyprtoolkit 0.5.4-5.1 -> 0.5.4-6However, omarchy update selects the older Omarchy package target and
reinstalls all three Hyprland-related packages at their current versions.
Replacing the running Hyprland executable makes its /proc/.../exe path show
as deleted, which triggers:
Hyprland has been updated. Reboot?This repeats on every update. Selecting No exits the current updater
without a reboot, but the update indicator returns.
Expected behavior
The update availability check and the package source used by the ARM updater
should agree. If Omarchy intentionally pins these packages, a newer regular
repository version should not keep the update indicator active. The updater
also should not reinstall unchanged running Hyprland packages and request a
reboot on every run.
Diagnostics
The terminal capture for this run is available locally at:
/tmp/omarchy-update.logIt shows that the system package transaction completed successfully, including
the lines warning: ... is up to date -- reinstalling for hyprland,hyprtoolkit, and hyprland-guiutils, followed by the reboot confirmation.
View raw text
### System details aarch64 with asahi ### What's wrong? # ARM update repeatedly requests a Hyprland reboot ## Summary On an aarch64/Asahi installation, `omarchy update` repeatedly requests a reboot because Hyprland was updated, although the Omarchy-pinned package versions have not changed. The system update indicator remains present after the update. ## Environment - Omarchy: `4.0.2-2` - Architecture: `aarch64` (Asahi) - Kernel: `linux-asahi 7.1.13.asahi3-1` - Hyprland: `0.56.2-3` - hyprland-guiutils: `0.2.2-3` - Installed hyprtoolkit: `0.5.4-5.1` ## Steps to reproduce 1. On an aarch64 Omarchy installation, ensure the regular `extra` repository provides a newer `hyprtoolkit` than the `omarchy` repository. 2. Run `omarchy update`. 3. Complete the update prompts. ## Actual behavior The updater explicitly targets these packages from the Omarchy repository: ```text omarchy/hyprland omarchy/hyprtoolkit omarchy/hyprland-guiutils ``` At the time of testing: ```text extra/hyprtoolkit: 0.5.4-6 omarchy/hyprtoolkit: 0.5.4-5.1 installed: 0.5.4-5.1 ``` `pacman -Qu` therefore continues to report: ```text hyprtoolkit 0.5.4-5.1 -> 0.5.4-6 ``` However, `omarchy update` selects the older Omarchy package target and reinstalls all three Hyprland-related packages at their current versions. Replacing the running Hyprland executable makes its `/proc/.../exe` path show as deleted, which triggers: ```text Hyprland has been updated. Reboot? ``` This repeats on every update. Selecting **No** exits the current updater without a reboot, but the update indicator returns. ## Expected behavior The update availability check and the package source used by the ARM updater should agree. If Omarchy intentionally pins these packages, a newer regular repository version should not keep the update indicator active. The updater also should not reinstall unchanged running Hyprland packages and request a reboot on every run. ## Diagnostics The terminal capture for this run is available locally at: ```text /tmp/omarchy-update.log ``` It shows that the system package transaction completed successfully, including the lines `warning: ... is up to date -- reinstalling` for `hyprland`, `hyprtoolkit`, and `hyprland-guiutils`, followed by the reboot confirmation.
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 14:55 UTC