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

No internet access, but WiFi connects

Reported by pmpinto · filed May 7, 2026Closed upstream on 2026-05-07 by its own reporter pmpinto. GitHub close reason: completed. Closed by its own reporter — not by itself 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

No internet access, but WiFi connectsrevision 1 · captured 2026-10-04 11:56 UTC via poll

System details

Omarchy 3.7.0, Framework Desktop, AMD Ryzen AI Max 300 S, AMD Radeon 8060S

What's wrong?

After upgrading to Omarchy 3.7.0, the machine connects to Wi-Fi successfully but has no working internet connectivity.

Initial symptoms:

  • Wi-Fi association succeeds
  • Router reachable locally
  • No DNS resolution
  • No internet access
  • Browser could not load anything

First checks:

ping 1.1.1.1

Result:

Destination Port Unreachable
sendmsg: Operation not permitted
ping google.com

Result:

Temporary failure in name resolution

Routing looked correct:

ip route

Result contained valid default route:

default via <router-ip> dev wlan0

Interface also had a valid IPv4:

ip addr show wlan0

Result contained:

inet <local-ip>/<mask>

Router reachable:

ping <router-ip>

This worked successfully.

Additional important observation:

  • Local LAN communication works correctly
  • Other local IPs are reachable, not just the router
  • mDNS/local hostname resolution also works:
  • homeassistant.local resolves correctly
  • Failure appears specifically related to outbound/WAN connectivity rather than general networking

DNS investigation:

resolvectl status

Observed:

  • interface marked routable
  • gateway assigned
  • DNS assigned correctly
  • DefaultRoute=yes

Direct resolver query:

resolvectl query google.com

Result:

resolve call failed: all attempts to contact name servers or networks failed

Forced DNS manually:

Edited:

/etc/systemd/resolved.conf

[Resolve]
DNS=1.1.1.1
DNSOverTLS=no

Restarted:

sudo systemctl restart systemd-resolved

Retested:

resolvectl query google.com

Same failure.

Resolver statistics:

resolvectl statistics

Observed:

  • timeouts increasing
  • no DNSSEC/protocol errors

Networking stack checks:

systemctl status systemd-networkd systemd-resolved iwd

All were:

active (running)

Further checks:

networkctl status wlan0

Observed:

  • State: routable
  • valid IPv4 address
  • gateway assigned
  • DNS assigned

Firewall checks:

  • nftables temporarily stopped
  • no change

Policy routing checks:

ip rule

Only standard entries:

  • local
  • main
  • default

RF checks:

rfkill list

No soft or hard blocks.

dmesg investigation:

dmesg | grep -Ei 'denied|wlan|auth'

Observed intermittent:

wlan0: denied authentication (status 33)

Additional isolation tests:

  • tested against phone tethering: same issue
  • disabled ASUS VPN Fusion on router: no change
  • older snapshots boot through Limine: same issue

Important isolation step:

Booted Omarchy live ISO (very old version).

Initially:

ping 1.1.1.1

returned:

network is unreachable

Then connected manually through:

iwctl

Commands used:

device list
station wlan0 scan
station wlan0 get-networks
station wlan0 connect <ssid>

After connecting from live ISO:

ping 1.1.1.1

worked successfully.

This became more interesting because:

  • same hardware
  • same Wi-Fi network
  • internet works correctly from the live environment after connecting through iwctl

This seems to isolate the issue to the installed userspace/configuration state rather than firmware or hardware.

What else can I do at this point? Could this have been caused by the recent 3.7.0 update? I'm hesitant to update the laptop now...

View raw text
### System details

Omarchy 3.7.0, Framework Desktop, AMD Ryzen AI Max 300 S, AMD Radeon 8060S

### What's wrong?

After upgrading to Omarchy 3.7.0, the machine connects to Wi-Fi successfully but has no working internet connectivity.

Initial symptoms:

* Wi-Fi association succeeds
* Router reachable locally
* No DNS resolution
* No internet access
* Browser could not load anything

First checks:

```bash
ping 1.1.1.1
```

Result:

```text
Destination Port Unreachable
sendmsg: Operation not permitted
```

```bash
ping google.com
```

Result:

```text
Temporary failure in name resolution
```

Routing looked correct:

```bash
ip route
```

Result contained valid default route:

```text
default via <router-ip> dev wlan0
```

Interface also had a valid IPv4:

```bash
ip addr show wlan0
```

Result contained:

```text
inet <local-ip>/<mask>
```

Router reachable:

```bash
ping <router-ip>
```

This worked successfully.

Additional important observation:

* Local LAN communication works correctly
* Other local IPs are reachable, not just the router
* mDNS/local hostname resolution also works:

  * `homeassistant.local` resolves correctly
* Failure appears specifically related to outbound/WAN connectivity rather than general networking

DNS investigation:

```bash
resolvectl status
```

Observed:

* interface marked routable
* gateway assigned
* DNS assigned correctly
* DefaultRoute=yes

Direct resolver query:

```bash
resolvectl query google.com
```

Result:

```text
resolve call failed: all attempts to contact name servers or networks failed
```

Forced DNS manually:

Edited:

```ini
/etc/systemd/resolved.conf

[Resolve]
DNS=1.1.1.1
DNSOverTLS=no
```

Restarted:

```bash
sudo systemctl restart systemd-resolved
```

Retested:

```bash
resolvectl query google.com
```

Same failure.

Resolver statistics:

```bash
resolvectl statistics
```

Observed:

* timeouts increasing
* no DNSSEC/protocol errors

Networking stack checks:

```bash
systemctl status systemd-networkd systemd-resolved iwd
```

All were:

```text
active (running)
```

Further checks:

```bash
networkctl status wlan0
```

Observed:

* State: routable
* valid IPv4 address
* gateway assigned
* DNS assigned

Firewall checks:

* nftables temporarily stopped
* no change

Policy routing checks:

```bash
ip rule
```

Only standard entries:

* local
* main
* default

RF checks:

```bash
rfkill list
```

No soft or hard blocks.

dmesg investigation:

```bash
dmesg | grep -Ei 'denied|wlan|auth'
```

Observed intermittent:

```text
wlan0: denied authentication (status 33)
```

Additional isolation tests:

* tested against phone tethering: same issue
* disabled ASUS VPN Fusion on router: no change
* older snapshots boot through Limine: same issue

Important isolation step:

Booted Omarchy live ISO (very old version).

Initially:

```bash
ping 1.1.1.1
```

returned:

```text
network is unreachable
```

Then connected manually through:

```bash
iwctl
```

Commands used:

```text
device list
station wlan0 scan
station wlan0 get-networks
station wlan0 connect <ssid>
```

After connecting from live ISO:

```bash
ping 1.1.1.1
```

worked successfully.

This became more interesting because:

* same hardware
* same Wi-Fi network
* internet works correctly from the live environment after connecting through `iwctl`

---

This seems to isolate the issue to the installed userspace/configuration state rather than firmware or hardware.

What else can I do at this point? Could this have been caused by the recent 3.7.0 update? I'm hesitant to update the laptop now...

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.