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

Bluetooth stop working since 3.7

Reported by Le-Chat-BottE · filed May 6, 2026Closed upstream on 2026-05-07 by its own reporter Le-Chat-BottE. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.

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 stop working since 3.7revision 1 · captured 2026-10-04 11:56 UTC via poll

System details

AMD AI Max+ 395 Omarchy 3.7.1

What's wrong?

When open bluetooth control, it says:
Error: internal error: D-Bus error org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.bluez
': unit failed

View raw text
### System details

AMD AI Max+ 395 Omarchy 3.7.1

### What's wrong?

When open bluetooth control, it says:
Error: internal error: D-Bus error org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.bluez
': unit failed

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.