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

systemctl and NetworkManager D-Bus calls time out on fresh Omarchy installation

Reported by kidelighost-ui · 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

systemctl and NetworkManager D-Bus calls time out on fresh Omarchy installationrevision 1 · captured 2026-09-28 21:24 UTC via poll

System details

AMD Ryzen 5 PRO 8500G with Radeon 740M Graphics - AMD Phoenix2 GPU - 14 GiB RAM - KIOXIA BG7 256GB NVMe - MediaTek MT7920 Wi-Fi (mt7921e) - Btrfs - Hyprland / Wayland - SDDM

What's wrong?

Summary

After a completely fresh Omarchy installation, multiple system-management D-Bus calls consistently time out. Basic networking still works over Ethernet, while Wi-Fi scanning works but connecting to Wi-Fi fails.

Reproduction:

On a fresh installation:
systemctl is-system-running
returns:
Failed to query system state: Connection timed out
The systemd Manager D-Bus interface also times out:
busctl introspect org.freedesktop.systemd1 \
/org/freedesktop/systemd1 \
org.freedesktop.systemd1.Manager
returns:
Failed to introspect object /org/freedesktop/systemd1 of service
org.freedesktop.systemd1: Connection timed out
NetworkManager itself responds to D-Bus introspection, but its permission method times out:
busctl call org.freedesktop.NetworkManager \
/org/freedesktop/NetworkManager \
org.freedesktop.NetworkManager \
GetPermissions
returns:
Call failed: Connection timed out
nmcli general permissions produces:
Error: Timeout 10 sec expired.
There is also a corresponding PAM/user-record timeout:
pam_systemd_home(sudo:auth): Failed to query user record: Connection timed out

Wi-Fi:

The MediaTek MT7920 is detected and the mt7921e driver is loaded.
rfkill reports:
Soft blocked: no
Hard blocked: no
nmcli device wifi list successfully scans nearby networks and sees them at up to 99–100% signal strength, but wlp4s0 remains disconnected and connection attempts time out.
Ethernet, DNS, and HTTPS work normally.

Additional boot error:

The kernel also reports:
amdgpu 0000:08:00.0: [drm] REG_WAIT timeout 1us * 100000 tries - optc314_disable_crtc
Plymouth also fails to terminate during boot:
plymouth-quit.service: start operation timed out. Terminating.
plymouth-quit.service: Failed with result 'timeout'.

Storage:

The KIOXIA BG7 initializes normally and Btrfs mounts successfully. I have not found obvious NVMe I/O errors, NVMe controller resets, NVMe timeouts, or Btrfs errors in the kernel log.

Notes:

This was a completely fresh installation after removing the previous OS/partitions.

I am not claiming the NVMe is defective; I am reporting the reproducible system-service/D-Bus timeouts and associated symptoms so they can be investigated.

The shutdown behavior may overlap with existing Omarchy shutdown issues, including #5832.

Is this combination of systemd Manager, NetworkManager permission, and PAM user-record timeouts a known issue?

View raw text
### System details

AMD Ryzen 5 PRO 8500G with Radeon 740M Graphics - AMD Phoenix2 GPU - 14 GiB RAM - KIOXIA BG7 256GB NVMe - MediaTek MT7920 Wi-Fi (`mt7921e`) - Btrfs - Hyprland / Wayland - SDDM

### What's wrong?

## Summary

After a completely fresh Omarchy installation, multiple system-management D-Bus calls consistently time out. Basic networking still works over Ethernet, while Wi-Fi scanning works but connecting to Wi-Fi fails.

Reproduction:

On a fresh installation:
systemctl is-system-running
returns:
Failed to query system state: Connection timed out
The systemd Manager D-Bus interface also times out:
busctl introspect org.freedesktop.systemd1 \
/org/freedesktop/systemd1 \
org.freedesktop.systemd1.Manager
returns:
Failed to introspect object /org/freedesktop/systemd1 of service
org.freedesktop.systemd1: Connection timed out
NetworkManager itself responds to D-Bus introspection, but its permission method times out:
busctl call org.freedesktop.NetworkManager \
/org/freedesktop/NetworkManager \
org.freedesktop.NetworkManager \
GetPermissions
returns:
Call failed: Connection timed out
`nmcli general permissions` produces:
Error: Timeout 10 sec expired.
There is also a corresponding PAM/user-record timeout:
pam_systemd_home(sudo:auth): Failed to query user record: Connection timed out

Wi-Fi:

The MediaTek MT7920 is detected and the `mt7921e` driver is loaded.
`rfkill` reports:
Soft blocked: no
Hard blocked: no
`nmcli device wifi list` successfully scans nearby networks and sees them at up to 99–100% signal strength, but `wlp4s0` remains disconnected and connection attempts time out.
Ethernet, DNS, and HTTPS work normally.

Additional boot error:

The kernel also reports:
amdgpu 0000:08:00.0: [drm] REG_WAIT timeout 1us * 100000 tries - optc314_disable_crtc
Plymouth also fails to terminate during boot:
plymouth-quit.service: start operation timed out. Terminating.
plymouth-quit.service: Failed with result 'timeout'.

Storage:

The KIOXIA BG7 initializes normally and Btrfs mounts successfully. I have not found obvious NVMe I/O errors, NVMe controller resets, NVMe timeouts, or Btrfs errors in the kernel log.

Notes:

This was a completely fresh installation after removing the previous OS/partitions.

I am not claiming the NVMe is defective; I am reporting the reproducible system-service/D-Bus timeouts and associated symptoms so they can be investigated.

The shutdown behavior may overlap with existing Omarchy shutdown issues, including #5832.

Is this combination of systemd Manager, NetworkManager permission, and PAM user-record timeouts a known issue?

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:12 UTC