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

Top-bar audio widget shows permanently 'muted' with no way to unmute when the sink is unresponsive

Reported by Hubert342 · filed Sep 13, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #8744 (R-1315). 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

Top-bar audio widget shows permanently 'muted' with no way to unmute when the sink is unresponsiverevision 1 · captured 2026-10-04 12:10 UTC via poll

Top-bar audio widget shows permanently "muted"/disabled with no way to unmute, when the underlying PipeWire sink is unresponsive

System

  • Omarchy (Hyprland + Quickshell-based omarchy shell)
  • pipewire 1.6.8, wireplumber 0.5.17
  • Affects the built-in omarchy.audio bar widget (/usr/share/omarchy/shell/plugins/panels/audio/Panel.qml)

Problem

On hardware where the default ALSA output sink is failing to actually open/resume in PipeWire (separate, hardware-specific bug — sink stuck in SUSPENDED, all playback hangs/times out, being reported to PipeWire separately), the Omarchy top-bar volume/sound icon shows the muted-speaker glyph and stays that way indefinitely:

  • Left-clicking the icon opens the panel, but the output toggle switch does not visibly unmute it.
  • Right-clicking (which calls toggleAllMuted()) does not change the displayed state either.
  • Restarting the shell (omarchy restart shell), restarting the full audio stack (omarchy restart audio), and even a full system reboot did not change the icon's stuck-muted appearance.
  • Meanwhile pactl get-sink-mute, amixer, and wpctl all agreed the ALSA/PipeWire mute state was no/off throughout — so the icon is not simply reflecting a real mute; it appears to be reading Pipewire.defaultAudioSink/volumeSink.audio.muted from a sink object that Quickshell's own PipeWire binding cannot get a live/consistent state for, since the same sink also never leaves the "SUSPENDED" state and can't actually be opened by any PipeWire client.

Suggested improvement

When hasOutput is true but the underlying sink is stuck/unresponsive (e.g. PwObjectTracker-bound node can't be read from default-nodes-api, or has been SUSPENDED for an unusually long time with failed open attempts), consider:
- Showing a distinct "output unavailable" state instead of a plain muted glyph, so users don't try to "unmute" something that isn't actually mutable, and
- Logging or otherwise surfacing that the sink resolution failed, to make this class of hardware-driver bug easier to distinguish from an actual accidental mute.

This is a UX/robustness suggestion arising from debugging a real hardware/driver bug on a specific laptop (HP Spectre x360, Meteor Lake, dual CS35L41 amps) — the root cause there is being reported upstream to PipeWire/kernel, but the Omarchy widget's inability to ever indicate "this isn't a normal mute" made it much harder to diagnose from the UI alone.

View raw text
# Top-bar audio widget shows permanently "muted"/disabled with no way to unmute, when the underlying PipeWire sink is unresponsive

## System
- Omarchy (Hyprland + Quickshell-based `omarchy shell`)
- pipewire 1.6.8, wireplumber 0.5.17
- Affects the built-in `omarchy.audio` bar widget (`/usr/share/omarchy/shell/plugins/panels/audio/Panel.qml`)

## Problem
On hardware where the default ALSA output sink is failing to actually open/resume in PipeWire (separate, hardware-specific bug — sink stuck in `SUSPENDED`, all playback hangs/times out, being reported to PipeWire separately), the Omarchy top-bar volume/sound icon shows the muted-speaker glyph and stays that way indefinitely:

- Left-clicking the icon opens the panel, but the output toggle switch does not visibly unmute it.
- Right-clicking (which calls `toggleAllMuted()`) does not change the displayed state either.
- Restarting the shell (`omarchy restart shell`), restarting the full audio stack (`omarchy restart audio`), and even a full system reboot did not change the icon's stuck-muted appearance.
- Meanwhile `pactl get-sink-mute`, `amixer`, and `wpctl` all agreed the ALSA/PipeWire mute state was `no`/`off` throughout — so the *icon* is not simply reflecting a real mute; it appears to be reading `Pipewire.defaultAudioSink`/`volumeSink.audio.muted` from a sink object that Quickshell's own PipeWire binding cannot get a live/consistent state for, since the same sink also never leaves the "SUSPENDED" state and can't actually be opened by any PipeWire client.

## Suggested improvement
When `hasOutput` is true but the underlying sink is stuck/unresponsive (e.g. `PwObjectTracker`-bound node can't be read from `default-nodes-api`, or has been `SUSPENDED` for an unusually long time with failed open attempts), consider:
- Showing a distinct "output unavailable" state instead of a plain muted glyph, so users don't try to "unmute" something that isn't actually mutable, and
- Logging or otherwise surfacing that the sink resolution failed, to make this class of hardware-driver bug easier to distinguish from an actual accidental mute.

This is a UX/robustness suggestion arising from debugging a real hardware/driver bug on a specific laptop (HP Spectre x360, Meteor Lake, dual CS35L41 amps) — the root cause there is being reported upstream to PipeWire/kernel, but the Omarchy widget's inability to ever indicate "this isn't a normal mute" made it much harder to diagnose from the UI alone.

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.