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

Wi-Fi panel can't forget the currently connected network, unlike the Bluetooth panel

Reported by thomasbrugman · filed Aug 27, 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

Wi-Fi panel can't forget the currently connected network, unlike the Bluetooth panelrevision 1 · captured 2026-09-28 21:24 UTC via poll

System details

Intel i7-8750H, Intel UHD 630 + AMD Radeon Pro 555X, Omarchy 4.0.1

What's wrong?

The network applet never offers the Forget action for the currently connected Wi-Fi network. The Bluetooth applet does not have this limitation: a connected device can be forgotten, and omarchy-bluetooth-device forget handles it by disconnecting first (bluetoothctl disconnect then bluetoothctl remove).

Steps to reproduce:

  1. Connect to a Wi-Fi network.
  2. Open the network panel.
  3. Hover or keyboard-select the connected network's row.
  4. No Forget action (󰅙) is offered. Other known-but-disconnected networks show it as expected.

Cause: the forget affordance is gated in shell/plugins/panels/network/Model.js:

function canForgetNetwork(network) {
  return !!(network && network.known && !network.connected)
}

so Panel.qml's forget path (network.forget()) is unreachable for the connected network.

Expected: parity with the Bluetooth panel — allow forgetting the connected network by disconnecting first, then removing the saved profile.

Happy to submit a PR mirroring the Bluetooth disconnect-then-forget behavior.

View raw text
### System details

Intel i7-8750H, Intel UHD 630 + AMD Radeon Pro 555X, Omarchy 4.0.1

### What's wrong?

The network applet never offers the Forget action for the **currently connected** Wi-Fi network. The Bluetooth applet does not have this limitation: a connected device can be forgotten, and `omarchy-bluetooth-device forget` handles it by disconnecting first (`bluetoothctl disconnect` then `bluetoothctl remove`).

**Steps to reproduce:**

1. Connect to a Wi-Fi network.
2. Open the network panel.
3. Hover or keyboard-select the connected network's row.
4. No Forget action (`󰅙`) is offered. Other known-but-disconnected networks show it as expected.

**Cause:** the forget affordance is gated in `shell/plugins/panels/network/Model.js`:

```js
function canForgetNetwork(network) {
  return !!(network && network.known && !network.connected)
}
```

so `Panel.qml`'s forget path (`network.forget()`) is unreachable for the connected network.

**Expected:** parity with the Bluetooth panel — allow forgetting the connected network by disconnecting first, then removing the saved profile.

Happy to submit a PR mirroring the Bluetooth disconnect-then-forget behavior.

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