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.
"Kernel has been updated. Reboot?" on every update on Arch ARM (linux-aarch64)
Reported by ericmoret · filed Sep 3, 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
Every time I run omarchy update I get the "Linux kernel has been updated. Reboot?" prompt, even when no kernel update happened and the running kernel already matches what's installed. Saying no is harmless and the rest of the update finishes fine, but it asks every time.
I'm running Omarchy in a UTM VM on an Apple Silicon Mac, so this is Arch Linux ARM with the linux-aarch64 kernel instead of x86 linux. I assume that's why it hasn't come up before.
The kernel-update check in bin/omarchy-update-restart looks for a vmlinuz in /usr/lib/modules/<version>/:
for kernel in /usr/lib/modules/*/vmlinuz; do
if [[ -f $kernel ]] && pacman -Qo "$kernel" &>/dev/null; then
installed_kernel=$(basename "$(dirname "$kernel")")
...On linux-aarch64 there's no vmlinuz there. That package ships the kernel image as /boot/Image and /boot/Image.gz, and /usr/lib/modules/<version>/ only holds the modules. So the glob matches nothing and the check always concludes the kernel changed.
$ uname -r
7.2.2-2-aarch64-ARCH
$ pacman -Q linux-aarch64
linux-aarch64 7.2.2-2
$ ls /usr/lib/modules/*/vmlinuz
ls: cannot access '/usr/lib/modules/*/vmlinuz': No such file or directory
$ pacman -Ql linux-aarch64 | grep /boot/
linux-aarch64 /boot/Image
linux-aarch64 /boot/Image.gzLooks the same on master.
System: Omarchy 4.0.2-4, Arch Linux ARM / aarch64, Hyprland 0.56.1, UTM (QEMU) guest on an Apple Silicon MacBook Air.
View raw text
Every time I run `omarchy update` I get the "Linux kernel has been updated. Reboot?" prompt, even when no kernel update happened and the running kernel already matches what's installed. Saying no is harmless and the rest of the update finishes fine, but it asks every time.
I'm running Omarchy in a UTM VM on an Apple Silicon Mac, so this is Arch Linux ARM with the `linux-aarch64` kernel instead of x86 `linux`. I assume that's why it hasn't come up before.
The kernel-update check in `bin/omarchy-update-restart` looks for a `vmlinuz` in `/usr/lib/modules/<version>/`:
```bash
for kernel in /usr/lib/modules/*/vmlinuz; do
if [[ -f $kernel ]] && pacman -Qo "$kernel" &>/dev/null; then
installed_kernel=$(basename "$(dirname "$kernel")")
...
```
On `linux-aarch64` there's no `vmlinuz` there. That package ships the kernel image as `/boot/Image` and `/boot/Image.gz`, and `/usr/lib/modules/<version>/` only holds the modules. So the glob matches nothing and the check always concludes the kernel changed.
```
$ uname -r
7.2.2-2-aarch64-ARCH
$ pacman -Q linux-aarch64
linux-aarch64 7.2.2-2
$ ls /usr/lib/modules/*/vmlinuz
ls: cannot access '/usr/lib/modules/*/vmlinuz': No such file or directory
$ pacman -Ql linux-aarch64 | grep /boot/
linux-aarch64 /boot/Image
linux-aarch64 /boot/Image.gz
```
Looks the same on `master`.
System: Omarchy 4.0.2-4, Arch Linux ARM / aarch64, Hyprland 0.56.1, UTM (QEMU) guest on an Apple Silicon MacBook Air.
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 10:42 UTC