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.
Bluetooth panel leaves discovery running after closing, causing DualSense disconnects in Steam games
Reported by EmilsValdmanis · filed Aug 13, 2026Closed upstream on 2026-08-13 by its own reporter EmilsValdmanis. GitHub close reason: completed. Closed by its own reporter — not by itself 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
Omarchy 4.0.0.r1689.g38542a1-1, Kernel 7.1.8-arch1-3, BlueZ 5.87-2, Bluetooth adapter Intel AX200
What's wrong?
Opening the Quattro Bluetooth panel starts device discovery, but closing the panel leaves the adapter in this state:
Discovering: yesWhile discovery remains active, my DualSense stops working shortly after entering a Steam game. Steam reports the controller as disconnected, while the Bluetooth panel and controller LED initially still indicate a connection.
Relevant logs:
bluetoothd: hidp_send_message() BT socket write error: Resource temporarily unavailable (11)
Steam: Controller device closed after hid_read failureRunning bluetoothctl scan off fails because discovery belongs to the Omarchy shell:
Failed to stop discovery: org.bluez.Error.FailedRestarting the shell releases the discovery request:
omarchy restart shellAfter confirming Discovering: no, the same controller and game work without disconnecting. The Bluetooth panel may need to stop its discovery request when it closes.
View raw text
### System details Omarchy 4.0.0.r1689.g38542a1-1, Kernel 7.1.8-arch1-3, BlueZ 5.87-2, Bluetooth adapter Intel AX200 ### What's wrong? Opening the Quattro Bluetooth panel starts device discovery, but closing the panel leaves the adapter in this state: ```text Discovering: yes ``` While discovery remains active, my DualSense stops working shortly after entering a Steam game. Steam reports the controller as disconnected, while the Bluetooth panel and controller LED initially still indicate a connection. Relevant logs: ```text bluetoothd: hidp_send_message() BT socket write error: Resource temporarily unavailable (11) Steam: Controller device closed after hid_read failure ``` Running `bluetoothctl scan off` fails because discovery belongs to the Omarchy shell: ```text Failed to stop discovery: org.bluez.Error.Failed ``` Restarting the shell releases the discovery request: ```bash omarchy restart shell ``` After confirming `Discovering: no`, the same controller and game work without disconnecting. The Bluetooth panel may need to stop its discovery request when it closes.
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.