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.
Passkey sign in with the QR code flow is not working in Chromium
Reported by muinmomin · filed Aug 10, 2025Closed upstream on 2025-08-22 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
Steps to reproduce:
1. Go to https://passkeys.io or https://webauthn.io
2. Click on Sign In (make sure you don't have a local passkey)
3. Scan QR code (I'm on an iPhone)
Will notice that the QR code in Chromium never disappears and the iPhone is stuck in the connecting screen.
Have confirmed:
1. Bluetooth in general works on the device (able to connect to Bluetooth devices successfully)
2. When the Bluetooth manager panel (triggered from Waybar) is open, the machine is in discoverable and pairable state.
3. chrome://device-log shows New caBLE device [MAC ADDRESS], Service data: [DATA], ([DATA]: no match v2), and then a bunch of Gatt services have not been fully resolved for device /org/bluez/hci0/dev_...
4. Ran all updates
Has anyone had luck with Chromium (would prefer to stick to the default and from official repo, especially for browsers) and passkeys with the QR code flow?
View raw text
Steps to reproduce: 1. Go to https://passkeys.io or https://webauthn.io 2. Click on Sign In (make sure you don't have a local passkey) 3. Scan QR code (I'm on an iPhone) Will notice that the QR code in Chromium never disappears and the iPhone is stuck in the connecting screen. Have confirmed: 1. Bluetooth in general works on the device (able to connect to Bluetooth devices successfully) 2. When the Bluetooth manager panel (triggered from Waybar) is open, the machine is in discoverable and pairable state. 3. chrome://device-log shows `New caBLE device [MAC ADDRESS]`, `Service data: [DATA]`, `([DATA]: no match v2)`, and then a bunch of `Gatt services have not been fully resolved for device /org/bluez/hci0/dev_...` 4. Ran all updates Has anyone had luck with Chromium (would prefer to stick to the default and from official repo, especially for browsers) and passkeys with the QR code flow?
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.