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.
Blue Yeti microphone detected but produces no capture after reboot
Reported by daveplatt71 · filed Sep 16, 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
System: GamingPC CPU: 13th Gen Intel Core i7-13700F (24 threads, 16 cores) GPU: NVIDIA GeForce RTX 4060 Ti RAM: 62 GiB OS: Omarchy 4.0.4-1 (stable) Kernel: Linux 7.2.5-3-omarchy Desktop: Hyprland 0.56.2 (Wayland) Audio: PipeWire 1.6.8, WirePlumber 0.5.17 Microphone: Logitech/Blue Yeti, USB ID 046d:0ab7, firmware 0.20
What's wrong?
On Omarchy, my Logitech/Blue Yeti microphone (046d:0ab7, firmware 0.20) was detected normally after reboot:
- PipeWire and WirePlumber were running
- The microphone appeared as the default input
- ALSA capture controls were enabled and unmuted
- PipeWire showed the capture node
- However, the hardware capture clock remained at zero and recordings contained no samples
Restarting PipeWire did not resolve it. The microphone only recovered after sending the Blue Yeti firmware reset command, equivalent to unplugging and
reconnecting the USB cable.
Installing and enabling blue-yeti-autoreset (https://github.com/lbrooney/blue-yeti-autoreset) restored capture immediately and produced a valid
recording. Its systemd service is now enabled to perform the reset once during boot.
This may be worth documenting in Omarchy’s audio troubleshooting guidance or including as an optional package/service for affected Blue Yeti devices.
Relevant details:
USB ID: 046d:0ab7
Firmware: 0.20
Audio stack: PipeWire 1.6.8 / WirePlumber 1.6.8
Device: Blue Microphones Analog Stereo
Symptom: Device detected, but capture samples remain at zero
Workaround: Firmware-level reset / physical USB reconnect
The recovery utility’s upstream explanation is here:
https://github.com/lbrooney/blue-yeti-autoreset
View raw text
### System details System: GamingPC CPU: 13th Gen Intel Core i7-13700F (24 threads, 16 cores) GPU: NVIDIA GeForce RTX 4060 Ti RAM: 62 GiB OS: Omarchy 4.0.4-1 (stable) Kernel: Linux 7.2.5-3-omarchy Desktop: Hyprland 0.56.2 (Wayland) Audio: PipeWire 1.6.8, WirePlumber 0.5.17 Microphone: Logitech/Blue Yeti, USB ID 046d:0ab7, firmware 0.20 ### What's wrong? On Omarchy, my Logitech/Blue Yeti microphone (046d:0ab7, firmware 0.20) was detected normally after reboot: - PipeWire and WirePlumber were running - The microphone appeared as the default input - ALSA capture controls were enabled and unmuted - PipeWire showed the capture node - However, the hardware capture clock remained at zero and recordings contained no samples Restarting PipeWire did not resolve it. The microphone only recovered after sending the Blue Yeti firmware reset command, equivalent to unplugging and reconnecting the USB cable. Installing and enabling blue-yeti-autoreset (https://github.com/lbrooney/blue-yeti-autoreset) restored capture immediately and produced a valid recording. Its systemd service is now enabled to perform the reset once during boot. This may be worth documenting in Omarchy’s audio troubleshooting guidance or including as an optional package/service for affected Blue Yeti devices. Relevant details: USB ID: 046d:0ab7 Firmware: 0.20 Audio stack: PipeWire 1.6.8 / WirePlumber 1.6.8 Device: Blue Microphones Analog Stereo Symptom: Device detected, but capture samples remain at zero Workaround: Firmware-level reset / physical USB reconnect The recovery utility’s upstream explanation is here: https://github.com/lbrooney/blue-yeti-autoreset
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 14:02 UTC