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

Bluetooth panel: Inquiry loop blocks connections (br-connection-page-timeout) & discovered devices flicker

Reported by WhiteWebDev · 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

Bluetooth panel: Inquiry loop blocks connections (br-connection-page-timeout) & discovered devices flickerrevision 1 · captured 2026-09-28 21:24 UTC via poll

What happened?

In Omarchy 4.0.1, the stock omarchy.bluetooth panel widget exhibits two bugs that prevent connecting to devices on single-radio controllers (like the Broadcom DW1820A):

  1. Inquiry loop starves the radio: While the panel is open, it forces continuous discovery. This constant inquiry competes with connection paging. When clicking to connect to a device while the panel is open, the connection attempt times out (br-connection-page-timeout) because the radio is busy scanning.
  2. Discovered devices flicker: In Model.js, visibleSections requires adapter.discovering to be true to show the 'discovered' section. When the scan pauses briefly, the entire discovered devices list disappears from the UI, making it impossible to interact with them consistently.

What was expected?

  • The panel should pause discovery when an outgoing connection is pending so the radio can complete the page request.
  • Devices that are already in the discovered cache should remain visible in the UI even if the active discovery scan pauses momentarily, to avoid UI flickering.

Steps to reproduce

  1. Open the Bluetooth panel.
  2. Attempt to connect to a device (especially on a weak or single-radio adapter like DW1820A).
  3. The connection fails with br-connection-page-timeout in the BlueZ logs because the panel keeps forcing discovery.
  4. Observe the 'Available' list disappearing as soon as discovery toggles off.

System details

  • Omarchy version: 4.0.1-1
  • Adapter: Broadcom BCM4350C5 (DW1820A)
View raw text
### What happened?
In Omarchy 4.0.1, the stock `omarchy.bluetooth` panel widget exhibits two bugs that prevent connecting to devices on single-radio controllers (like the Broadcom DW1820A):

1. **Inquiry loop starves the radio:** While the panel is open, it forces continuous discovery. This constant inquiry competes with connection paging. When clicking to connect to a device while the panel is open, the connection attempt times out (`br-connection-page-timeout`) because the radio is busy scanning.
2. **Discovered devices flicker:** In `Model.js`, `visibleSections` requires `adapter.discovering` to be true to show the 'discovered' section. When the scan pauses briefly, the entire discovered devices list disappears from the UI, making it impossible to interact with them consistently.

### What was expected?
- The panel should pause discovery when an outgoing connection is pending so the radio can complete the page request.
- Devices that are already in the discovered cache should remain visible in the UI even if the active discovery scan pauses momentarily, to avoid UI flickering.

### Steps to reproduce
1. Open the Bluetooth panel.
2. Attempt to connect to a device (especially on a weak or single-radio adapter like DW1820A).
3. The connection fails with `br-connection-page-timeout` in the BlueZ logs because the panel keeps forcing discovery.
4. Observe the 'Available' list disappearing as soon as discovery toggles off.

### System details
- Omarchy version: 4.0.1-1
- Adapter: Broadcom BCM4350C5 (DW1820A)

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