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.
ASUS audio soft-mixer fix only initializes ALC285, leaving other Realtek codecs (ALC294) muted
Reported by nitine · filed Aug 19, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #4821 (R-2013). 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
System details
ASUS ROG Flow X13 GV301QH, AMD Ryzen HD Audio, Realtek ALC294, Omarchy 4.0.0-1
What's wrong?
install/user/hardware/asus/fix-audio-mixer.sh applies the ALSA soft mixer to every ASUS ROG machine by DMI match, but the compensating hardware unmute only fires when aplay -l matches ALC285, and it only raises Master. On ROG laptops with another Realtek codec — ALC294 on the Flow X13 here — the block is a no-op, and since the soft mixer stops PipeWire from managing the hardware mixer, the codec's default-muted Headphone/Speaker controls stay at 0% [off] forever. Result: PipeWire shows analog-output-headphones selected, unmuted, with an active stream, but no sound. Replugging the jack re-mutes the hardware control, so a one-off manual amixer fix doesn't stick.
Reproduce: any ROG laptop with a non-ALC285 Realtek codec → run install → plug headphones → amixer -c <card> sget Headphone shows 0% [off] while wpctl status shows the sink running and unmuted.
Same mechanism as #4821 (ALC285, where only Headphone/Speaker are missed) — this is the general case: every ROG codec other than ALC285 gets the soft mixer's downside with none of the mitigation. fix-mic.sh has the same ALC285 literal, so those machines miss the capture unmute (#4771) too.
View raw text
### System details ASUS ROG Flow X13 GV301QH, AMD Ryzen HD Audio, Realtek ALC294, Omarchy 4.0.0-1 ### What's wrong? `install/user/hardware/asus/fix-audio-mixer.sh` applies the ALSA soft mixer to every ASUS ROG machine by DMI match, but the compensating hardware unmute only fires when `aplay -l` matches `ALC285`, and it only raises `Master`. On ROG laptops with another Realtek codec — ALC294 on the Flow X13 here — the block is a no-op, and since the soft mixer stops PipeWire from managing the hardware mixer, the codec's default-muted `Headphone`/`Speaker` controls stay at `0% [off]` forever. Result: PipeWire shows `analog-output-headphones` selected, unmuted, with an active stream, but no sound. Replugging the jack re-mutes the hardware control, so a one-off manual `amixer` fix doesn't stick. Reproduce: any ROG laptop with a non-ALC285 Realtek codec → run install → plug headphones → `amixer -c <card> sget Headphone` shows `0% [off]` while `wpctl status` shows the sink running and unmuted. Same mechanism as #4821 (ALC285, where only `Headphone`/`Speaker` are missed) — this is the general case: every ROG codec other than ALC285 gets the soft mixer's downside with none of the mitigation. `fix-mic.sh` has the same `ALC285` literal, so those machines miss the capture unmute (#4771) too.
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.