Proof Portal

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

Audio panel per-application sliders do not receive pointer input

Reported by sgersz · filed Sep 1, 2026 · 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

Audio panel per-application sliders do not receive pointer inputrevision 1 · captured 2026-09-28 21:24 UTC via poll

System details

  • Omarchy 4.0.1-1
  • Quickshell 0.3.1-1
  • PipeWire 1.6.8-1
  • WirePlumber 0.5.15-1
  • Hyprland 0.56.2
  • Qt 6.11.2
  • Kernel 7.1.9-arch1-2
  • CPU/GPU: AMD Ryzen AI MAX+ 395 / Radeon 8060S
  • Current quattro commit checked: b686ed892d9c3020c3336203f6d34cc75b544e2b

omarchy debug --no-sudo --print was unavailable on this installation (Unknown Omarchy command).

What's wrong?

The per-application playback sliders under Audio → Sources do not respond to mouse presses or dragging. This affects multiple PipeWire streams, including Zen Browser and a Wine application (eqgame.exe). The master output slider and keyboard volume controls work normally.

PipeWire exposes the streams correctly, and their displayed percentages match pactl list sink-inputs; only pointer interaction with the inline sliders is broken.

Steps to reproduce

  1. Start an application that is actively playing audio.
  2. Open the Omarchy audio panel.
  3. Find the application under Sources.
  4. Click or drag its inline volume slider.

Actual result

The slider does not move and the application's PipeWire stream volume does not change.

Expected result

The slider should move and update that application's stream volume.

Suspected cause

StreamRow ends with a full-row MouseArea declared after the PanelSlider:

MouseArea {
  anchors.fill: parent
  hoverEnabled: true
  acceptedButtons: Qt.NoButton
  propagateComposedEvents: true
  onContainsMouseChanged: if (containsMouse) {
    root.cursorActive = true
    root.focusSection = "streams"
    root.selectedIndex = streamRow.rowIndex
  }
}

In this configuration, the row-level pointer item sits above the inline PanelSlider and prevents its MouseArea from receiving press/drag interaction.

Verified workaround/fix

Replacing the row-level MouseArea with a HoverHandler preserves cursor tracking without covering the slider:

HoverHandler {
  onHoveredChanged: if (hovered) {
    root.cursorActive = true
    root.focusSection = "streams"
    root.selectedIndex = streamRow.rowIndex
  }
}

This was tested through a cloned omarchy.audio plugin. After hot reload, both Zen and eqgame.exe sliders immediately became interactive and correctly changed their PipeWire stream volumes.

The same blocking MouseArea is still present in the current quattro branch at shell/plugins/panels/audio/Panel.qml.

View raw text
## System details

- Omarchy `4.0.1-1`
- Quickshell `0.3.1-1`
- PipeWire `1.6.8-1`
- WirePlumber `0.5.15-1`
- Hyprland `0.56.2`
- Qt `6.11.2`
- Kernel `7.1.9-arch1-2`
- CPU/GPU: AMD Ryzen AI MAX+ 395 / Radeon 8060S
- Current `quattro` commit checked: `b686ed892d9c3020c3336203f6d34cc75b544e2b`

`omarchy debug --no-sudo --print` was unavailable on this installation (`Unknown Omarchy command`).

## What's wrong?

The per-application playback sliders under **Audio → Sources** do not respond to mouse presses or dragging. This affects multiple PipeWire streams, including Zen Browser and a Wine application (`eqgame.exe`). The master output slider and keyboard volume controls work normally.

PipeWire exposes the streams correctly, and their displayed percentages match `pactl list sink-inputs`; only pointer interaction with the inline sliders is broken.

## Steps to reproduce

1. Start an application that is actively playing audio.
2. Open the Omarchy audio panel.
3. Find the application under **Sources**.
4. Click or drag its inline volume slider.

### Actual result

The slider does not move and the application's PipeWire stream volume does not change.

### Expected result

The slider should move and update that application's stream volume.

## Suspected cause

`StreamRow` ends with a full-row `MouseArea` declared after the `PanelSlider`:

```qml
MouseArea {
  anchors.fill: parent
  hoverEnabled: true
  acceptedButtons: Qt.NoButton
  propagateComposedEvents: true
  onContainsMouseChanged: if (containsMouse) {
    root.cursorActive = true
    root.focusSection = "streams"
    root.selectedIndex = streamRow.rowIndex
  }
}
```

In this configuration, the row-level pointer item sits above the inline `PanelSlider` and prevents its `MouseArea` from receiving press/drag interaction.

## Verified workaround/fix

Replacing the row-level `MouseArea` with a `HoverHandler` preserves cursor tracking without covering the slider:

```qml
HoverHandler {
  onHoveredChanged: if (hovered) {
    root.cursorActive = true
    root.focusSection = "streams"
    root.selectedIndex = streamRow.rowIndex
  }
}
```

This was tested through a cloned `omarchy.audio` plugin. After hot reload, both Zen and `eqgame.exe` sliders immediately became interactive and correctly changed their PipeWire stream volumes.

The same blocking `MouseArea` is still present in the current `quattro` branch at `shell/plugins/panels/audio/Panel.qml`.

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 10:22 UTC