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

# Bug Report: Network Panel shows "NOT CONNECTED" for active 802.1x Enterprise (eduroam) networks

Reported by Pabl0125 · filed Sep 15, 2026Closed upstream on 2026-10-12 by the bot omarchybot, as a duplicate (target not recorded).

Decided: Out of scope — decided by agents · verified 3 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

# Bug Report: Network Panel shows "NOT CONNECTED" for active 802.1x Enterprise (eduroam) networksrevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

OS: Omarchy 4.0.3-1 (Linux 7.2.3-arch1-3) - WM: Hyprland 0.56.2 (Wayland) - Shell: Quickshell 0.3.1 - NetworkManager: Version 1.58.1-1 - Hardware: HP Gaming Laptop (Intel i7-13700H, RTX 4050 / Iris Xe)

What's wrong?

Description

When successfully connecting to an 802.1x Enterprise Wi-Fi network (such as eduroam), the Quickshell network panel fails to recognize the connection state. The top of the panel displays a crossed-out Wi-Fi icon and the text "NOT CONNECTED", even though the connection is fully active.

Interestingly, the panel simultaneously displays the correct IP Address, Gateway, Ping, and real-time traffic metrics, proving the system is aware of the active connection.

Steps to Reproduce

  1. Configure and connect to an 802.1x Enterprise network (e.g., eduroam) using nmcli.
  2. Ensure the connection is active and the system has an IP address.
  3. Open the Omarchy network panel.
  4. Observe the panel header showing "NOT CONNECTED" despite the metrics working.

Expected Behavior

The panel should recognize the active enterprise connection, display "CONNECTED" (or the network name), and show the appropriate Wi-Fi signal icon.

Actual Behavior

The panel header falls back to "NOT CONNECTED" and a disconnected icon, while the lower half of the widget correctly displays the active IP address and network traffic.

Technical Context & Possible Cause

The issue appears to be in the QML logic for the network panel, likely in /usr/share/omarchy/shell/plugins/panels/network/Panel.qml.

The kind property evaluates to "disconnected" because connectedWifiNetwork evaluates to null.
In the findConnectedWifiNetwork() function:

function findConnectedWifiNetwork() {
  var networks = wifiNetworkObjects || []
  for (var i = 0; i < networks.length; i++) {
    if (networks[i] && networks[i].connected) return networks[i]
  }
  return null
}

It seems that for 802.1x Enterprise networks, the backend service wrapper fails to set .connected = true on the corresponding network object in wifiNetworkObjects, causing the UI to default to a disconnected state.

View raw text
### System details

**OS:** Omarchy 4.0.3-1 (Linux 7.2.3-arch1-3) - **WM:** Hyprland 0.56.2 (Wayland) - **Shell:** Quickshell 0.3.1 - **NetworkManager:** Version 1.58.1-1 - **Hardware:** HP Gaming Laptop (Intel i7-13700H, RTX 4050 / Iris Xe)

### What's wrong?

## Description
When successfully connecting to an 802.1x Enterprise Wi-Fi network (such as eduroam), the Quickshell network panel fails to recognize the connection state. The top of the panel displays a crossed-out Wi-Fi icon and the text "NOT CONNECTED", even though the connection is fully active. 

Interestingly, the panel simultaneously displays the correct IP Address, Gateway, Ping, and real-time traffic metrics, proving the system is aware of the active connection.

## Steps to Reproduce
1. Configure and connect to an 802.1x Enterprise network (e.g., eduroam) using `nmcli`.
2. Ensure the connection is active and the system has an IP address.
3. Open the Omarchy network panel.
4. Observe the panel header showing "NOT CONNECTED" despite the metrics working.

## Expected Behavior
The panel should recognize the active enterprise connection, display "CONNECTED" (or the network name), and show the appropriate Wi-Fi signal icon.

## Actual Behavior
The panel header falls back to "NOT CONNECTED" and a disconnected icon, while the lower half of the widget correctly displays the active IP address and network traffic.

## Technical Context & Possible Cause
The issue appears to be in the QML logic for the network panel, likely in `/usr/share/omarchy/shell/plugins/panels/network/Panel.qml`.

The `kind` property evaluates to `"disconnected"` because `connectedWifiNetwork` evaluates to `null`. 
In the `findConnectedWifiNetwork()` function:
```qml
function findConnectedWifiNetwork() {
  var networks = wifiNetworkObjects || []
  for (var i = 0; i < networks.length; i++) {
    if (networks[i] && networks[i].connected) return networks[i]
  }
  return null
}
```
It seems that for 802.1x Enterprise networks, the backend service wrapper fails to set `.connected = true` on the corresponding network object in `wifiNetworkObjects`, causing the UI to default to a disconnected state.

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 13:47 UTC