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

Bluetooth re-enables itself after every reboot, even when toggled off

Reported by heymaikol · filed May 9, 2026Closed upstream on 2026-05-11 by the merge of PR #5683 (closed by dhh). GitHub close reason: completed.

Open at source
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

Bluetooth re-enables itself after every reboot, even when toggled offrevision 1 · captured 2026-10-04 11:56 UTC via poll

System details

Intel i5-13400 / NVIDIA RTX 3060 (+ Intel UHD 730 iGPU) / Intel AX211 Bluetooth / Omarchy 3.7.1

What's wrong?

Turning Bluetooth off bluetui doesn't survive a reboot
(the controller comes back up powered on after a reboot)

Why: /etc/bluetooth/main.conf ships with AutoEnable=true (BlueZ default), which forces controllers on at boot regardless of the persisted Powered state in /var/lib/bluetooth/<MAC>/settings.

Expected: The last user-set power state should persist across reboots, the same way most desktop OSes behave.

Repro:

  1. bluetui → toggle controller off
  2. Reboot
  3. Bluetooth is on again

Fix: Set AutoEnable=false in /etc/bluetooth/main.conf. PR #5683 does this for fresh installs and via migration for existing setups.

View raw text
### System details

Intel i5-13400 / NVIDIA RTX 3060 (+ Intel UHD 730 iGPU) / Intel AX211 Bluetooth / Omarchy 3.7.1

### What's wrong?

Turning Bluetooth off `bluetui` doesn't survive a reboot 
(the controller comes back up powered on after a reboot)

**Why:** `/etc/bluetooth/main.conf` ships with `AutoEnable=true` (BlueZ default), which forces controllers on at boot regardless of the persisted `Powered` state in `/var/lib/bluetooth/<MAC>/settings`.

**Expected:** The last user-set power state should persist across reboots, the same way most desktop OSes behave.

**Repro:**

1. `bluetui` → toggle controller off
2. Reboot
3. Bluetooth is on again

**Fix:** Set `AutoEnable=false` in `/etc/bluetooth/main.conf`. PR #5683 does this for fresh installs and via migration for existing setups.

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.