Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-2833GitHub issuePublicReceived

Mark which drive I booted from

Reported by wkoszek · filed Sep 10, 2025Closed upstream on 2025-09-11 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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

Mark which drive I booted fromrevision 1 · captured 2026-10-04 11:35 UTC via poll

System details

Framework 13 with AMD

What's wrong?

I got couple of 256GB USB Extension Cards from Framework, and I'm using them to try custom setups.

I used Caligula to write ISO to 1 Extension card and use it to boot from it. I'm then trying to install Omarchy on another Extension Card that's also 256GB.

The problem: I can't see which is ISO drive and which is my target destination NVM. Both are the same size, so it's just either I see sda or sub and I don't think there's a guarantee that's always sda that I booted from.

Great improvement would be to show which drive we booted from. I also don't know if it makes sense to show the drive we booted from in the installer at all? Is it possible to boot from drive and then pick it as destination during the install?

Alternative: give me spare terminal for some debugging before installing. Some distros offer this.

View raw text
### System details

Framework 13 with AMD 

### What's wrong?

I got couple of 256GB USB Extension Cards from Framework, and I'm using them to try custom setups. 

I used Caligula to write ISO to 1 Extension card and use it to boot from it. I'm then trying to install Omarchy on another Extension Card that's also 256GB.

The problem: I can't see which is ISO drive and which is my target destination NVM. Both are the same size, so it's just either I see sda or sub and I don't think there's a guarantee that's always sda that I booted from.

Great improvement would be to show which drive we booted from. I also don't know if it makes sense to show the drive we booted from in the installer at all? Is it possible to boot from drive and then pick it as destination during the install?

Alternative: give me spare terminal for some debugging before installing. Some distros offer this.

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.