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

Volume key auto-repeat floods pipewire-pulse clients and becomes laggy

Reported by Yiteng-CHEN · filed Sep 14, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 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

Volume key auto-repeat floods pipewire-pulse clients and becomes laggyrevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

Apple MacBookAir6,2 (Intel Core i5-4260U / Intel Haswell i915), Omarchy 4.0.2-1, Linux 7.1.9-arch1-2, Hyprland 0.56.2-1, PipeWire/pipewire-pulse 1.6.8-1, WirePlumber 0.5.15-1. Stock Hyprland input repeat settings (repeat_rate = 40, repeat_delay = 250) and the stock repeating output-volume bindings are in use. The default output is a physical ALSA sink; no custom PipeWire quantum or DSP configuration is present.

What's wrong?

Holding the output-volume hardware keys (XF86AudioRaiseVolume / XF86AudioLowerVolume, F11/F12 on this MacBook) makes volume changes and the OSD visibly lag. At the same time, the user journal reports bursts such as:

pipewire-pulse: too many client application connections: Connection refused

I observed 113 occurrences on September 11 and 37 occurrences within two seconds on September 14.

Steps to reproduce:

  1. Keep Omarchy's stock repeating output-volume bindings and stock input repeat rate.
  2. Run journalctl --user -fu pipewire-pulse.service.
  3. Hold the volume-up or volume-down hardware key.
  4. Observe delayed volume/OSD updates and the connection-refused messages above.

The repeatable binding calls omarchy-audio-output-volume up to 40 times per second. Each adjustment currently starts several short-lived pactl clients while resolving the sink, reading state, changing it, and refreshing the OSD. On this machine, overlapping invocations exhaust pipewire-pulse's client capacity.

Expected behavior: holding a volume key should adjust volume smoothly without exhausting pipewire-pulse client connections.

A nonblocking per-user flock around repeatable adjustment actions fixes the issue by dropping only overlapping repeats. Mute remains independent and responsive. I have a tested patch and will link the PR here.

View raw text
### System details

Apple MacBookAir6,2 (Intel Core i5-4260U / Intel Haswell i915), Omarchy 4.0.2-1, Linux 7.1.9-arch1-2, Hyprland 0.56.2-1, PipeWire/pipewire-pulse 1.6.8-1, WirePlumber 0.5.15-1. Stock Hyprland input repeat settings (`repeat_rate = 40`, `repeat_delay = 250`) and the stock repeating output-volume bindings are in use. The default output is a physical ALSA sink; no custom PipeWire quantum or DSP configuration is present.

### What's wrong?

Holding the output-volume hardware keys (`XF86AudioRaiseVolume` / `XF86AudioLowerVolume`, F11/F12 on this MacBook) makes volume changes and the OSD visibly lag. At the same time, the user journal reports bursts such as:

```text
pipewire-pulse: too many client application connections: Connection refused
```

I observed 113 occurrences on September 11 and 37 occurrences within two seconds on September 14.

Steps to reproduce:

1. Keep Omarchy's stock repeating output-volume bindings and stock input repeat rate.
2. Run `journalctl --user -fu pipewire-pulse.service`.
3. Hold the volume-up or volume-down hardware key.
4. Observe delayed volume/OSD updates and the connection-refused messages above.

The repeatable binding calls `omarchy-audio-output-volume` up to 40 times per second. Each adjustment currently starts several short-lived `pactl` clients while resolving the sink, reading state, changing it, and refreshing the OSD. On this machine, overlapping invocations exhaust pipewire-pulse's client capacity.

Expected behavior: holding a volume key should adjust volume smoothly without exhausting pipewire-pulse client connections.

A nonblocking per-user `flock` around repeatable adjustment actions fixes the issue by dropping only overlapping repeats. Mute remains independent and responsive. I have a tested patch and will link the PR here.

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 13:19 UTC