[GH-ISSUE #1166] Volume module does not respect default sink #8782

New issue

Closed

opened 2026-05-23 03:54:17 +01:00 by JakeStanger · 2 comments

JakeStanger commented

2026-05-23 03:54:17 +01:00

Owner

Originally created by @bandithedoge on GitHub (Sep 17, 2025).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1166

Describe the bug
I'm using PipeWire's PA server implementation. I have two available output devices, an audio interface and a filter chain node (which is set as the default output). When starting Ironbar with the volume module enabled, it instantly sets the audio interface as the default output and reroutes all running apps.

Sometimes this randomly happens with changes in the audio system, such as skipping a song in MPD.

To reproduce
Steps to reproduce the behavior:

Create a Filter-Chain node in PipeWire and set it as the default output
Add module volume
Run Ironbar
Observe the audio output changes

Expected behavior
Volume module keeps the default audio output selected.

System information:

Distro: NixOS
Compositor: Niri
Ironbar version: master (0.17.0)

Configuration

Config

{
  type = "volume";
  format = "${icon "{icon}"} {percentage}%";
  icons = {
    volume_high = "󰕾";
    volume_medium = "󰖀";
    volume_low = "󰕿";
    muted = "󰝟";
  };
  on_scroll_up = "wpctl set-volume @DEFAULT_AUDIO_SINK@ 1%+";
  on_scroll_down = "wpctl set-volume @DEFAULT_AUDIO_SINK@ 1%-";
}

Originally created by @bandithedoge on GitHub (Sep 17, 2025). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1166 **Describe the bug** I'm using PipeWire's PA server implementation. I have two available output devices, an audio interface and a filter chain node (which is set as the default output). When starting Ironbar with the volume module enabled, it instantly sets the audio interface as the default output and reroutes all running apps. Sometimes this randomly happens with changes in the audio system, such as skipping a song in MPD. **To reproduce** Steps to reproduce the behavior: 1. Create a Filter-Chain node in PipeWire and set it as the default output 2. Add module `volume` 3. Run Ironbar 4. Observe the audio output changes **Expected behavior** Volume module keeps the default audio output selected. **System information:** - Distro: NixOS - Compositor: Niri - Ironbar version: master (0.17.0) **Configuration** <details><summary>Config</summary> ```nix { type = "volume"; format = "${icon "{icon}"} {percentage}%"; icons = { volume_high = "󰕾"; volume_medium = "󰖀"; volume_low = "󰕿"; muted = "󰝟"; }; on_scroll_up = "wpctl set-volume @DEFAULT_AUDIO_SINK@ 1%+"; on_scroll_down = "wpctl set-volume @DEFAULT_AUDIO_SINK@ 1%-"; } ``` </details>

JakeStanger

2026-05-23 03:54:17 +01:00

closed this issue
added the
T:Bug

P:Medium

A:Client

M:Volume
labels

JakeStanger commented

2026-05-23 03:54:17 +01:00

Author

Owner

@JakeStanger commented on GitHub (Apr 28, 2026):

Not fully resolved, but #1475 should go a way to helping this

@JakeStanger commented on GitHub (Apr 28, 2026): Not fully resolved, but #1475 should go a way to helping this

JakeStanger commented

2026-05-23 03:54:17 +01:00

Author

Owner

@JakeStanger commented on GitHub (May 9, 2026):

I think #1482 should fully resolve this now, so going to close. If this still occurs let me know.

@JakeStanger commented on GitHub (May 9, 2026): I think #1482 should fully resolve this now, so going to close. If this still occurs let me know.