Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
Audio volume resolver misses effect_input/effect_output filter-chain pairs
Reported by omarchybot · filed Oct 4, 2026 · 2 revisionsClosed upstream on 2026-10-04 by the merge of PR #14241 (closed by dhh). GitHub close reason: completed.
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
The EasyEffects-specific fix in #13396 has merged, but the separate filter-chain reproduction in #12204 remains outside it.
The reported default sink is effect_input.Dolby_Balanced, while its downstream sink-input is named effect_output.Dolby_Balanced and targets the physical ALSA sink. In current quattro, omarchy-audio-output-sink matches a sink-input only when its node name starts with the virtual sink name. That test cannot match this pair, and the new PipeWire-link lookup is gated on easyeffects_sink. The resolver consequently returns the virtual input rather than the downstream hardware output, so volume keys and the audio panel control the wrong stage.
The broader proposal #12299 was closed without merging its generic mapping. This issue preserves that remaining report separately from the now-fixed EasyEffects case. The mechanism is supported by current source and the reporter’s reproduction; no fresh hardware reproduction or tests were run in this cleanup.
Scope checked by GPT-6 in Codex and Codex Medium; review independence is not guaranteed.
Omabot on behalf of DHH
View raw text
The EasyEffects-specific fix in [#13396](https://github.com/omacom/omarchy/pull/13396) has merged, but the [separate filter-chain reproduction in #12204](https://github.com/omacom/omarchy/issues/12204#issuecomment-5720888866) remains outside it. The reported default sink is `effect_input.Dolby_Balanced`, while its downstream sink-input is named `effect_output.Dolby_Balanced` and targets the physical ALSA sink. In current `quattro`, `omarchy-audio-output-sink` matches a sink-input only when its node name starts with the virtual sink name. That test cannot match this pair, and the new PipeWire-link lookup is gated on `easyeffects_sink`. The resolver consequently returns the virtual input rather than the downstream hardware output, so volume keys and the audio panel control the wrong stage. The broader proposal [#12299](https://github.com/omacom/omarchy/pull/12299) was closed without merging its generic mapping. This issue preserves that remaining report separately from the now-fixed EasyEffects case. The mechanism is supported by current source and the reporter’s reproduction; no fresh hardware reproduction or tests were run in this cleanup. Scope checked by GPT-6 in Codex and Codex Medium; review independence is not guaranteed. Omabot on behalf of DHH
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.