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.
MSI X370 GAMING PLUS (ALC892): 3.5 mm jack hotplug only works after PipeWire restart
Reported by dandresrp · filed Apr 17, 2026 · open at source
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
System details
MSI X370 GAMING PLUS (MS-7A33), AMD Family 17h HD Audio Controller [1022:1457], Realtek ALC892 (Subsystem Id 0x1462fa33), Omarchy 3.5.1, Linux 6.19.10-arch1-1
What's wrong?
On this exact board, plugging or unplugging 3.5 mm headphones does not trigger reliable hotplug detection. The headphones only become available after restarting PipeWire or WirePlumber manually.
I validated this as a kernel/HDA powersave interaction on this hardware:
- evtest /dev/input/event25 showed no reliable SW_HEADPHONE_INSERT events with the default snd_hda_intel settings
- hda-verb /dev/snd/hwC1D0 0x1b GET_PIN_SENSE 0 oscillated with power_save=10 and power_save_controller=Y
- after setting snd_hda_intel power_save=0 power_save_controller=N, jack detection became stable immediately
- PipeWire then started emitting change/remove/new events for the card and sink on each unplug/replug, and the active port switched to analog-output-headphones without restarting audio services
I have a PR ready that adds an exact-hardware workaround for:
- board vendor: MSI
- board name: X370 GAMING PLUS (MS-7A33)
- codec: Realtek ALC892
- subsystem id: 0x1462fa33
The workaround installs:
options snd_hda_intel power_save=0 power_save_controller=Ninto /etc/modprobe.d/90-snd-hda-intel-jackfix.conf, applies it during install, and also ships a migration for existing users.
I can provide additional debug output if needed, including the exact codec#0 dump and omarchy-debug.
View raw text
### System details MSI X370 GAMING PLUS (MS-7A33), AMD Family 17h HD Audio Controller [1022:1457], Realtek ALC892 (Subsystem Id 0x1462fa33), Omarchy 3.5.1, Linux 6.19.10-arch1-1 ### What's wrong? On this exact board, plugging or unplugging 3.5 mm headphones does not trigger reliable hotplug detection. The headphones only become available after restarting PipeWire or WirePlumber manually. I validated this as a kernel/HDA powersave interaction on this hardware: - `evtest /dev/input/event25` showed no reliable `SW_HEADPHONE_INSERT` events with the default `snd_hda_intel` settings - `hda-verb /dev/snd/hwC1D0 0x1b GET_PIN_SENSE 0` oscillated with `power_save=10` and `power_save_controller=Y` - after setting `snd_hda_intel power_save=0 power_save_controller=N`, jack detection became stable immediately - PipeWire then started emitting `change/remove/new` events for the card and sink on each unplug/replug, and the active port switched to `analog-output-headphones` without restarting audio services I have a PR ready that adds an exact-hardware workaround for: - board vendor: `MSI` - board name: `X370 GAMING PLUS (MS-7A33)` - codec: `Realtek ALC892` - subsystem id: `0x1462fa33` The workaround installs: ```conf options snd_hda_intel power_save=0 power_save_controller=N ``` into `/etc/modprobe.d/90-snd-hda-intel-jackfix.conf`, applies it during install, and also ships a migration for existing users. I can provide additional debug output if needed, including the exact `codec#0` dump and `omarchy-debug`.
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 02:47 UTC