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 script doesn't detect custom/alternative kernels
Reported by revan1611 · filed Nov 4, 2025Closed upstream on 2025-11-05 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
System details
Omarchy 3.1.5, CachyOS kernel (original "linux" kernel removed), asus rog strix g713rw
What's wrong?
What happened:
When running Omarchy-Update with a custom (alternative) kernel (and the original 'linux' kernel removed), at the end of the process the script reports 'linux' kernel not found and always suggests a reboot, even though the system is running on a valid alternative kernel.
Steps to reproduce:
1. Install any alternative/custom kernel and remove the original 'linux' kernel.
2. Run the Omarchy-Update script.
3. Notice the message 'linux' kernel not found and that a reboot is always recommended at the end, regardless of kernel status.
Expected behavior:
- Omarchy-Update should recognize and support systems running a custom/alternative kernel (no unnecessary error or reboot prompt just because the original 'linux' kernel is missing).
Additional context:
This behavior may cause confusion for users who run custom kernels, leading to unnecessary reboots or concerns about system integrity. See attached log for system details and errors: KLdc.log
View raw text
### System details Omarchy 3.1.5, CachyOS kernel (original "linux" kernel removed), asus rog strix g713rw ### What's wrong? **What happened:** When running Omarchy-Update with a custom (alternative) kernel (and the original 'linux' kernel removed), at the end of the process the script reports `'linux' kernel not found` and always suggests a reboot, even though the system is running on a valid alternative kernel. **Steps to reproduce:** 1. Install any alternative/custom kernel and remove the original 'linux' kernel. 2. Run the Omarchy-Update script. 3. Notice the message `'linux' kernel not found` and that a reboot is always recommended at the end, regardless of kernel status. **Expected behavior:** - Omarchy-Update should recognize and support systems running a custom/alternative kernel (no unnecessary error or reboot prompt just because the original 'linux' kernel is missing). **Additional context:** This behavior may cause confusion for users who run custom kernels, leading to unnecessary reboots or concerns about system integrity. See attached log for system details and errors: [KLdc.log](https://github.com/user-attachments/files/23340647/KLdc.log)
- KLdc.log
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.