Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
Can't get internet access on any captive portal for airport / hotel Wi-Fi.
Reported by coolaj86 · filed Sep 21, 2025Closed upstream on 2026-07-18 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
System details
2025 Framework Laptop 13
What's wrong?
I've got a buddy on the phone right now who would be reporting this issue, except that he can't get connected to do it.
He's been through two airports and two hotels yesterday and today and hasn't been able to access the internet after clicking through the captive portals.
4 failures in a row over two days (and no successes) seems like more than just bad luck.
Omarchy was installed from the 3.0.1 ISO - so it's a fairly fresh install and no custom network setup as far as I'm aware.
This seems weird to me because my understanding is that the captive portal usually is done through DNS hijacking and a mac address whitelist... so I don't know why it would work on an iPhone just fine and not on Omarchy. I'll update if we figure out what's going wrong.
Updates
- Tried http://captive.apple.com and http://example.com, but they can't be reached after triggering the portal
- My guess is that it's related to some sort of DNS over HTTPS or whatever the local resolver running on 127.0.0.53 is doing
- Updating /etc/resolve.conf to use nameserver 1.1.1.3 did not fix it
- Internet IP addresses can be pinged. It seems to just be DNS.
View raw text
### System details 2025 Framework Laptop 13 ### What's wrong? I've got a buddy on the phone right now who would be reporting this issue, except that he can't get connected to do it. He's been through two airports and two hotels yesterday and today and hasn't been able to access the internet after clicking through the captive portals. 4 failures in a row over two days (and no successes) seems like more than just bad luck. Omarchy was installed from the 3.0.1 ISO - so it's a fairly fresh install and no custom network setup as far as I'm aware. This seems weird to me because my understanding is that the captive portal usually is done through DNS hijacking and a mac address whitelist... so I don't know why it would work on an iPhone just fine and not on Omarchy. I'll update if we figure out what's going wrong. _Updates_ - Tried http://captive.apple.com and http://example.com, but they can't be reached after triggering the portal - My guess is that it's related to some sort of DNS over HTTPS or whatever the local resolver running on 127.0.0.53 is doing - Updating `/etc/resolve.conf` to use `nameserver 1.1.1.3` did not fix it - Internet IP addresses can be pinged. It seems to just be DNS.
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.