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 iso 3.0.1 attempts to install to the wrong storage
Reported by Lejoni · filed Sep 24, 2025Closed upstream on 2025-09-26 by ryanrhughes. 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
AMD 9950X3D 64GB RAM RTX 3080
What's wrong?
I very clearly selected to install to nvme0n1
and when confirming it also said nvme0n1
but install tried to format sda instead. witch is one of my raid HDDs.
I disconnected all the SATA discs (sda - sdc) and then the installation worked perfectly.
I would think this is a very critical bug as it could result in data loss without user error.
~ ❯ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 3.6T 0 disk
├─sda1 8:1 0 1M 0 part
├─sda2 8:2 0 3.7G 0 part
│ └─md0 9:0 0 3.7G 0 raid1
├─sda3 8:3 0 93.1G 0 part
│ └─md1 9:1 0 93.1G 0 raid1
└─sda4 8:4 0 3.5T 0 part
└─md2 9:2 0 3.5T 0 raid1
sdb 8:16 0 3.6T 0 disk
├─sdb1 8:17 0 1M 0 part
├─sdb2 8:18 0 3.7G 0 part
│ └─md0 9:0 0 3.7G 0 raid1
├─sdb3 8:19 0 93.1G 0 part
│ └─md1 9:1 0 93.1G 0 raid1
└─sdb4 8:20 0 3.5T 0 part
└─md2 9:2 0 3.5T 0 raid1
sdc 8:32 0 2.7T 0 disk
├─sdc1 8:33 0 977M 0 part
└─sdc2 8:34 0 2.7T 0 part
zram0 252:0 0 4G 0 disk [SWAP]
nvme0n1 259:0 0 1.8T 0 disk
├─nvme0n1p1 259:1 0 2G 0 part /boot
└─nvme0n1p2 259:2 0 1.8T 0 part
└─root 253:0 0 1.8T 0 crypt /home
/var/cache/pacman/pkg
/var/log
/```View raw text
### System details
AMD 9950X3D 64GB RAM RTX 3080
### What's wrong?
I very clearly selected to install to nvme0n1
and when confirming it also said nvme0n1
but install tried to format sda instead. witch is one of my raid HDDs.
I disconnected all the SATA discs (sda - sdc) and then the installation worked perfectly.
I would think this is a very critical bug as it could result in data loss without user error.
```
~ ❯ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 3.6T 0 disk
├─sda1 8:1 0 1M 0 part
├─sda2 8:2 0 3.7G 0 part
│ └─md0 9:0 0 3.7G 0 raid1
├─sda3 8:3 0 93.1G 0 part
│ └─md1 9:1 0 93.1G 0 raid1
└─sda4 8:4 0 3.5T 0 part
└─md2 9:2 0 3.5T 0 raid1
sdb 8:16 0 3.6T 0 disk
├─sdb1 8:17 0 1M 0 part
├─sdb2 8:18 0 3.7G 0 part
│ └─md0 9:0 0 3.7G 0 raid1
├─sdb3 8:19 0 93.1G 0 part
│ └─md1 9:1 0 93.1G 0 raid1
└─sdb4 8:20 0 3.5T 0 part
└─md2 9:2 0 3.5T 0 raid1
sdc 8:32 0 2.7T 0 disk
├─sdc1 8:33 0 977M 0 part
└─sdc2 8:34 0 2.7T 0 part
zram0 252:0 0 4G 0 disk [SWAP]
nvme0n1 259:0 0 1.8T 0 disk
├─nvme0n1p1 259:1 0 2G 0 part /boot
└─nvme0n1p2 259:2 0 1.8T 0 part
└─root 253:0 0 1.8T 0 crypt /home
/var/cache/pacman/pkg
/var/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.