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-1471GitHub issuePublicDecided· Out of scope

Lid close suspends USB-root Omarchy and tears down the session

Reported by I-No-oNe · filed Aug 25, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 4 days ago.

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?
AreaOutside the audited area· Decided by agents · verified
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?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Lid close suspends USB-root Omarchy and tears down the sessionrevision 1 · captured 2026-09-28 21:24 UTC via poll

System details

  • Lenovo V14 G2 ALC
  • AMD Ryzen 5 5500U with integrated Radeon graphics
  • Omarchy 4.0.0-1
  • Hyprland 0.56.2
  • Kernel 7.1.8-arch1-3
  • Root filesystem: encrypted Btrfs on a SanDisk USB 3.2 drive (/dev/sda); the internal NVMe is not the root disk

What is wrong?

Omarchy is installed on a portable USB drive and booted directly from it. Closing the laptop lid enters deep suspend. A low-level system screen appears, the graphical session disappears, and the open applications are lost. The following boot reports both system and user journals as corrupted or uncleanly shut down.

This has reproduced repeatedly on the same USB-root installation.

Relevant journal lines from the failed session:

systemd-logind: suspend requested from client PID 8441 (systemctl) (unit [email protected])...
systemd-logind: The system will suspend now!
omarchy-shell: lock-requested
omarchy-shell: secure=true
kernel: PM: suspend entry (deep)

Storage layout confirms that the running installation is on USB:

sda         usb  disk  SanDisk 3.2Gen1
├─sda1           part  vfat        /boot
└─sda2           part  crypto_LUKS
  └─root         crypt btrfs       /home /var/log /

Steps to reproduce

  1. Boot an Omarchy installation whose root filesystem is on a removable USB drive.
  2. Start a graphical session and open applications.
  3. Close the laptop lid.
  4. Reopen it or reboot after the failed sleep transition.

Expected behavior

Omarchy should detect that the root backing device uses USB transport and avoid suspend on lid close. Locking or ignoring the lid event is safer, and Suspend should ideally be disabled in the system menu for that boot. This must be connector and host independent because the same drive moves between laptops.

Local workaround

  • Set HandleLidSwitch, HandleLidSwitchExternalPower, and HandleLidSwitchDocked to ignore in a logind drop-in.
  • Override the Hyprland switch:on:Lid Switch binding so it only runs omarchy-hyprland-monitor-clamshell.
  • Enable the existing suspend-off Omarchy toggle.
View raw text
### System details

- Lenovo V14 G2 ALC
- AMD Ryzen 5 5500U with integrated Radeon graphics
- Omarchy 4.0.0-1
- Hyprland 0.56.2
- Kernel 7.1.8-arch1-3
- Root filesystem: encrypted Btrfs on a SanDisk USB 3.2 drive (`/dev/sda`); the internal NVMe is not the root disk

### What is wrong?

Omarchy is installed on a portable USB drive and booted directly from it. Closing the laptop lid enters deep suspend. A low-level system screen appears, the graphical session disappears, and the open applications are lost. The following boot reports both system and user journals as corrupted or uncleanly shut down.

This has reproduced repeatedly on the same USB-root installation.

Relevant journal lines from the failed session:

```text
systemd-logind: suspend requested from client PID 8441 (systemctl) (unit [email protected])...
systemd-logind: The system will suspend now!
omarchy-shell: lock-requested
omarchy-shell: secure=true
kernel: PM: suspend entry (deep)
```

Storage layout confirms that the running installation is on USB:

```text
sda         usb  disk  SanDisk 3.2Gen1
├─sda1           part  vfat        /boot
└─sda2           part  crypto_LUKS
  └─root         crypt btrfs       /home /var/log /
```

### Steps to reproduce

1. Boot an Omarchy installation whose root filesystem is on a removable USB drive.
2. Start a graphical session and open applications.
3. Close the laptop lid.
4. Reopen it or reboot after the failed sleep transition.

### Expected behavior

Omarchy should detect that the root backing device uses USB transport and avoid suspend on lid close. Locking or ignoring the lid event is safer, and Suspend should ideally be disabled in the system menu for that boot. This must be connector and host independent because the same drive moves between laptops.

### Local workaround

- Set `HandleLidSwitch`, `HandleLidSwitchExternalPower`, and `HandleLidSwitchDocked` to `ignore` in a logind drop-in.
- Override the Hyprland `switch:on:Lid Switch` binding so it only runs `omarchy-hyprland-monitor-clamshell`.
- Enable the existing `suspend-off` Omarchy toggle.

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.

  • Out of scopeDecided by agents · verified · 2026-10-09 09:54 UTC