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.
Use sudo for /boot file checks in limine-snapper.sh
Reported by 2312nimit · filed Jul 24, 2026Closed upstream on 2026-07-31 by its own reporter 2312nimit. GitHub close reason: completed. Closed by its own reporter — not by itself 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
i5-12450HX ,RTX3050 , 16GB RAM
What's wrong?
On systems where /boot is a vfat partition mounted with fmask=0077 (the default in Omarchy's fstab), the install fails at limine-snapper.sh with "Error: Limine config not found" even though limine.conf exists and limine is installed.
The root cause: limine-snapper.sh uses [[ -f /boot/... ]] and grep to locate and read the limine config. These are bash builtins/stat calls that respect file permissions — on vfat with fmask=0077, files appear mode 000 to non-root users, so the tests always return false.
Fix: Replace all bare [[ -f /boot/... ]] and grep /boot/... calls in limine-snapper.sh with sudo test -f and sudo grep, consistent with the rest of the script which already uses sudo for all /boot writes.
Affected lines: 14-23 (config detection), 29 (cmdline read), 50 (pre-delete check), 89, 93 (post-install verification).
links: https://github.com/niraletter/omaniri/commit/ffcbc9fe2c31bda523c4849bf48b5a53fb78ef0a
View raw text
### System details i5-12450HX ,RTX3050 , 16GB RAM ### What's wrong? On systems where /boot is a vfat partition mounted with fmask=0077 (the default in Omarchy's fstab), the install fails at limine-snapper.sh with "Error: Limine config not found" even though limine.conf exists and limine is installed. The root cause: limine-snapper.sh uses [[ -f /boot/... ]] and grep to locate and read the limine config. These are bash builtins/stat calls that respect file permissions — on vfat with fmask=0077, files appear mode 000 to non-root users, so the tests always return false. Fix: Replace all bare [[ -f /boot/... ]] and grep /boot/... calls in limine-snapper.sh with sudo test -f and sudo grep, consistent with the rest of the script which already uses sudo for all /boot writes. Affected lines: 14-23 (config detection), 29 (cmdline read), 50 (pre-delete check), 89, 93 (post-install verification). links: https://github.com/niraletter/omaniri/commit/ffcbc9fe2c31bda523c4849bf48b5a53fb78ef0a
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.