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.
Omarchy Update Issue: Persistent Reboot Prompt
Reported by thrillho93 · filed Aug 14, 2025Closed upstream on 2025-08-22 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
When running omarchy-update through the menu, I'm repeatedly prompted to reboot my machine with the message "New Linux kernel requires reboot. Ready?" even after multiple reboots.
System Information
- Current kernel version: 6.16.0-arch2-1
pacman -Q linux
linux 6.16.arch2-1hostnamectl
Operating System: Arch Linux
Kernel: Linux 6.16.0-arch2…
Architecture: x86-64
Hardware Vendor: Lenovogrep -i "linux " /var/log/pacman.log | grep upgraded
[2025-08-14T08:03:34-0500] [ALPM] upgraded linux (6.15.9.arch1-1 -> 6.16.arch2-1)Steps to Reproduce
- Run
omarchy updatefrom the menu - Enter sudo password when prompted
- System shows "New Linux kernel requires reboot. Ready?" message
- Reboot the system
- Run
omarchy updateagain - Notice the same reboot prompt appears
Expected Behavior
After rebooting, the system should recognize that I'm already running the latest kernel and not prompt for another reboot.
Additional Context
This issue began occurring after the kernel upgrade on August 14th. I have rebooted multiple times, but the prompt persists despite the fact that I'm already running the latest kernel version (6.16.0-arch2-1).
View raw text
When running `omarchy-update` through the menu, I'm repeatedly prompted to reboot my machine with the message `"New Linux kernel requires reboot. Ready?"` even after multiple reboots.
### System Information
- Current kernel version: 6.16.0-arch2-1
```
pacman -Q linux
linux 6.16.arch2-1
```
```
hostnamectl
Operating System: Arch Linux
Kernel: Linux 6.16.0-arch2…
Architecture: x86-64
Hardware Vendor: Lenovo
```
```
grep -i "linux " /var/log/pacman.log | grep upgraded
[2025-08-14T08:03:34-0500] [ALPM] upgraded linux (6.15.9.arch1-1 -> 6.16.arch2-1)
```
### Steps to Reproduce
1. Run `omarchy update` from the menu
2. Enter sudo password when prompted
3. System shows "New Linux kernel requires reboot. Ready?" message
4. Reboot the system
5. Run `omarchy update` again
6. Notice the same reboot prompt appears
### Expected Behavior
After rebooting, the system should recognize that I'm already running the latest kernel and not prompt for another reboot.
### Additional Context
This issue began occurring after the kernel upgrade on August 14th. I have rebooted multiple times, but the prompt persists despite the fact that I'm already running the latest kernel version (6.16.0-arch2-1).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.