Proof Portal

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-4055GitHub issuePublicReceived

After upgrade - iwctl device list is empty - until systemctl restart iwd

Reported by realaaa · filed Jan 21, 2026Closed upstream on 2026-02-01 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

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

After upgrade - iwctl device list is empty - until systemctl restart iwdrevision 1 · captured 2026-10-04 11:49 UTC via poll

System details

ThinkPad L14 Gen 6 (AMD) and Omarchy 3.3.3 now

What's wrong?

hi guys !

similar to this one - https://www.reddit.com/r/archlinux/comments/tgxsyy/iwctl_device_list_gives_an_empty_table/ - so it may be upstream Arch bug maybe?

anyhow if you know anything or can push me to the right direction.

  • first upgrade left system badly broken and without Wifi
  • managed to connect to Wifi by doing systemctl restart iwd
  • this triggers iwctl to start seeing the device - before that device list is empty
  • installed available packages - reboot and almost back to normal now

BUT - still need to do "systemctl restart iwd" before iwctl can see the device and connect to Wifi

not a blocker, but definitely some sort of a bug - please halp !

View raw text
### System details

ThinkPad L14 Gen 6 (AMD) and Omarchy 3.3.3 now

### What's wrong?

hi guys ! 

similar to this one - https://www.reddit.com/r/archlinux/comments/tgxsyy/iwctl_device_list_gives_an_empty_table/ - so it may be upstream Arch bug maybe? 

anyhow if you know anything or can push me to the right direction.

- first upgrade left system badly broken and without Wifi
- managed to connect to Wifi by doing systemctl restart iwd
- this triggers iwctl to start seeing the device - before that device list is empty
- installed available packages - reboot and almost back to normal now

BUT - still need to do "systemctl restart iwd" before iwctl can see the device and connect to Wifi 

not a blocker, but definitely some sort of a bug - please halp !

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.