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

Virtual sinks/sources (like Easy Effects) force volume to 100% on creation/destruction and trigger audio scripts with empty arguments.

Reported by rodrigo-castilla · filed Sep 21, 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

Virtual sinks/sources (like Easy Effects) force volume to 100% on creation/destruction and trigger audio scripts with empty arguments.revision 1 · captured 2026-09-28 21:23 UTC via poll

System details

13th Gen Intel(R) Core(TM) i7-13650HX (12+8) @ 4.90 GHz, GeForce RTX 4060 Max-Q / Mobile, Omarchy 4.0.4-1

What's wrong?

Problem description

Currently, when a virtual audio sink/source is created or destroyed (e.g., launching or closing Easy Effects), the volume level is forcefully reset to 100%, ignoring the previous volume state.

I expected the system to either remember the previous hardware volume or inherit the current master volume when transitioning between the physical hardware and the virtual node. Instead, the transition always maxes out the volume.

Steps to reproduce

  1. Set the system input/output volume to 20%.
  2. Launch Easy Effects (creating easyeffects_sink). The volume spikes to 100%.
  3. Set the volume back to 20%.
  4. Close Easy Effects (returning to the hardware node). The volume spikes to 100% again.

Debugging context

  • I verified WirePlumber's default-routes state file, and the correct volume percentages (e.g., 0.54) are being saved for the hardware nodes. WirePlumber isn't losing the state.
  • I added debug logging to ./bin/omarchy-audio-input-set-default to intercept the transition.
  • The debug log revealed that when Easy Effects opens/closes, the script is executed, but the $node_id and $source_name arguments are passed as empty strings
  • Because the arguments are empty, wpctl set-default and pactl set-default-source fail, and the sudden appearance/disappearance of the virtual node causes the UI/daemon to default the channel to 100%.

Expected behavior

  1. The event listener (likely in omarchy-shell or the daemon monitoring audio changes) should pass valid node IDs/names when virtual nodes appear.
  2. The logic should implement volume inheritance: if a newly created virtual node doesn't have a known volume history, it should inherit the volume of the node it's replacing, rather than defaulting to 100%.
View raw text
### System details

13th Gen Intel(R) Core(TM) i7-13650HX (12+8) @ 4.90 GHz, GeForce RTX 4060 Max-Q / Mobile, Omarchy 4.0.4-1

### What's wrong?

## Problem description
Currently, when a virtual audio sink/source is created or destroyed (e.g., launching or closing Easy Effects), the volume level is forcefully reset to 100%, ignoring the previous volume state.

I expected the system to either remember the previous hardware volume or inherit the current master volume when transitioning between the physical hardware and the virtual node. Instead, the transition always maxes out the volume.

## Steps to reproduce 
1. Set the system input/output volume to 20%.
2. Launch Easy Effects (creating easyeffects_sink). The volume spikes to 100%.
3. Set the volume back to 20%.
4. Close Easy Effects (returning to the hardware node). The volume spikes to 100% again.

## Debugging context
- I verified WirePlumber's default-routes state file, and the correct volume percentages (e.g., 0.54) are being saved for the hardware nodes. WirePlumber isn't losing the state.
- I added debug logging to ./bin/omarchy-audio-input-set-default to intercept the transition.
- The debug log revealed that when Easy Effects opens/closes, the script is executed, but the $node_id and $source_name arguments are passed as empty strings
- Because the arguments are empty, wpctl set-default and pactl set-default-source fail, and the sudden appearance/disappearance of the virtual node causes the UI/daemon to default the channel to 100%.

## Expected behavior
1. The event listener (likely in omarchy-shell or the daemon monitoring audio changes) should pass valid node IDs/names when virtual nodes appear.
2. The logic should implement volume inheritance: if a newly created virtual node doesn't have a known volume history, it should inherit the volume of the node it's replacing, rather than defaulting to 100%.

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 17:00 UTC