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.
Advisory: install to NVMe *with* SSD causes issues on older MSI laptop
Reported by houstonhaynes · filed Nov 21, 2025Closed upstream on 2025-11-21. 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
MSI GL63 laptop with SSD and NVMe
What's wrong?
This is an issue I resolved but I wanted to leave a note here in case anyone ran into a similar issue. I have an older MSI laptop (GL63) that I decided to put this OS on "for kicks" and it LOVE it!
The point of friction that I ran into was not obvious, as it showed up as a time-out on boot that dumped to the emergency prompt. I first suspected the NVidia drivers (this laptop runs an RTX2060-ish mobile GPU) but the timeout made me suspect it might be the drive configuration. So I went to Claude/Gemini and got the note back that the UUID (which in the cmdline was cryptdevice=PARTUUID= didn't match the UUID of the device I had installed the OS to.
After some head-scratching and troubleshooting I tried it the old fashioned way - I pulled the SSD and re-installed with only the NVMe on the system, and it went without a hitch. I re-installed the secondary SSD manually mounted and everything was fine.
I'm not as familiar with this stack, but the UUID that's in place now is most definitely different than the one that was there when both drives were in place during the first install(s).
View raw text
### System details MSI GL63 laptop with SSD and NVMe ### What's wrong? This is an issue I resolved but I wanted to leave a note here in case anyone ran into a similar issue. I have an older MSI laptop (GL63) that I decided to put this OS on "for kicks" and it *LOVE* it! The point of friction that I ran into was not obvious, as it showed up as a time-out on boot that dumped to the emergency prompt. I first suspected the NVidia drivers (this laptop runs an RTX2060-ish mobile GPU) but the timeout made me suspect it might be the drive configuration. So I went to Claude/Gemini and got the note back that the UUID (which in the cmdline was `cryptdevice=PARTUUID=` didn't match the UUID of the device I had installed the OS to. After some head-scratching and troubleshooting I tried it the old fashioned way - I pulled the SSD and re-installed with only the NVMe on the system, and it went without a hitch. I re-installed the secondary SSD manually mounted and everything was fine. I'm not as familiar with this stack, but the UUID that's in place now is most definitely different than the one that was there when both drives were in place during the first install(s).
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.