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

Apple Silicon: speakersafetyd start-limit leaves speakers locked with volume UI at 100%

Reported by ijt · filed Sep 23, 2026Closed upstream on 2026-10-08 by the bot omarchybot, as not planned.

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

Apple Silicon: speakersafetyd start-limit leaves speakers locked with volume UI at 100%revision 1 · captured 2026-09-28 21:23 UTC via poll

System details

Apple M1 MacBook Air J313, Asahi / Omarchy 4.0.3rc4-1, PipeWire 1.6.8, speakersafetyd 2.0.1-1

What's wrong?

Screen recording with desktop + mic audio (wf-recorder backend on Asahi) can panic speakersafetyd (Left: Negative power, bad ivsense data?) while the speaker PCM is at 96 kHz. The stock unit is Restart=on-failure with StartLimitBurst=10 / StartLimitInterval=60. After ten crashes systemd hits start-limit-hit and stops restarting. macaudio then clamps speaker playback volume to a 0–1 range (Speaker Volume Unlock=0). PipeWire/wpctl still report 100% and unmuted, so YouTube, X, etc. go silent with no mute indicator.

This is not #10970 (loudnorm writing 96 kHz AAC files) and not #10858 (WirePlumber teardown after resume). Those are related Asahi audio failures with different daemons and triggers.

Steps to reproduce

  1. On Apple Silicon Omarchy, record with desktop + microphone audio (menu path that passes --with-desktop-audio --with-microphone-audio).
  2. Stop the recording.
  3. Play YouTube or any local audio. Volume OSD still shows 100%; speakers are silent.
  4. systemctl is-failed speakersafetyd is failed (start-limit-hit).
  5. amixer -c AppleJ313 cget name='Speaker Volume Unlock' reads values=0; Left/Right Speaker Playback Volume max=1.
  6. pkexec systemctl reset-failed speakersafetyd && pkexec systemctl start speakersafetyd unlocks the amps (max=201, Unlock=1) and sound returns.

Expected

speakersafetyd keeps retrying after the 96 kHz client goes away, the amps unlock, and the desktop says something if they stay locked.

Journal excerpt from a J313:

speakersafetyd: PCM rate: 96000..96000
speakersafetyd: Left: Negative power, bad ivsense data? (-1.2564131)
systemd: speakersafetyd.service: Failed with result 'start-limit-hit'.
View raw text
### System details

Apple M1 MacBook Air J313, Asahi / Omarchy 4.0.3rc4-1, PipeWire 1.6.8, speakersafetyd 2.0.1-1

### What's wrong?

Screen recording with desktop + mic audio (wf-recorder backend on Asahi) can panic `speakersafetyd` (`Left: Negative power, bad ivsense data?`) while the speaker PCM is at 96 kHz. The stock unit is `Restart=on-failure` with `StartLimitBurst=10` / `StartLimitInterval=60`. After ten crashes systemd hits `start-limit-hit` and **stops restarting**. macaudio then clamps speaker playback volume to a 0–1 range (`Speaker Volume Unlock=0`). PipeWire/wpctl still report 100% and unmuted, so YouTube, X, etc. go silent with no mute indicator.

This is not #10970 (loudnorm writing 96 kHz AAC *files*) and not #10858 (WirePlumber teardown after resume). Those are related Asahi audio failures with different daemons and triggers.

#### Steps to reproduce

1. On Apple Silicon Omarchy, record with desktop + microphone audio (menu path that passes `--with-desktop-audio --with-microphone-audio`).
2. Stop the recording.
3. Play YouTube or any local audio. Volume OSD still shows 100%; speakers are silent.
4. `systemctl is-failed speakersafetyd` is `failed` (`start-limit-hit`).
5. `amixer -c AppleJ313 cget name='Speaker Volume Unlock'` reads `values=0`; Left/Right Speaker Playback Volume `max=1`.
6. `pkexec systemctl reset-failed speakersafetyd && pkexec systemctl start speakersafetyd` unlocks the amps (`max=201`, Unlock=1) and sound returns.

#### Expected

`speakersafetyd` keeps retrying after the 96 kHz client goes away, the amps unlock, and the desktop says something if they stay locked.

Journal excerpt from a J313:

```
speakersafetyd: PCM rate: 96000..96000
speakersafetyd: Left: Negative power, bad ivsense data? (-1.2564131)
systemd: speakersafetyd.service: Failed with result 'start-limit-hit'.
```

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.