[GH-ISSUE #1140] Volume module crash with PipeWire #1758

New issue

Closed

opened 2026-05-22 22:54:32 +01:00 by JakeStanger · 2 comments

JakeStanger commented

2026-05-22 22:54:32 +01:00

Owner

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

Describe the bug
After about a minute of idling, Ironbar crashes with the following message:

Assertion 'q->front' failed at ../src/pulsecore/queue.c:81, function pa_queue_push(). Aborting.
fish: Job 1, 'ironbar' terminated by signal SIGABRT (Abort)

To reproduce
Steps to reproduce the behavior:

Add module volume
Run ironbar
Wait

Expected behavior
No crashes.

System information:

Distro: NixOS unstable
Compositor: Niri
Ironbar version: master

Configuration

Config

programs.ironbar = {
  enable = true;
  config = {
    # ...
    end = [{
      type = "volume";
      icons = {
        volume_high = "󰕾";
        volume_medium = "󰖀";
        volume_low = "󰕿";
        muted = "󰝟";
      };
    }];
    # ...
  };
};

Originally created by @bandithedoge on GitHub (Sep 4, 2025). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1140 **Describe the bug** After about a minute of idling, Ironbar crashes with the following message: ``` Assertion 'q->front' failed at ../src/pulsecore/queue.c:81, function pa_queue_push(). Aborting. fish: Job 1, 'ironbar' terminated by signal SIGABRT (Abort) ``` **To reproduce** Steps to reproduce the behavior: 1. Add module `volume` 2. Run `ironbar` 3. Wait **Expected behavior** No crashes. **System information:** - Distro: NixOS unstable - Compositor: Niri - Ironbar version: master **Configuration**  <details><summary>Config</summary> ```nix programs.ironbar = { enable = true; config = { # ... end = [{ type = "volume"; icons = { volume_high = "󰕾"; volume_medium = "󰖀"; volume_low = "󰕿"; muted = "󰝟"; }; }]; # ... }; }; ``` </details>

JakeStanger

2026-05-22 22:54:32 +01:00

closed this issue
added the
T:Bug

M:Volume

P:Critical

A:Client
labels

JakeStanger commented

2026-05-22 22:54:32 +01:00

Author

Owner

@JakeStanger commented on GitHub (Sep 5, 2025):

I'm going to need some more information for this one, as I run with pipewire-pulse with no issues.

Firstly can you confirm it's pipewire-pulse you're using, and could you get a version for that please?

Secondly can you run with IRONBAR_LOG=ironbar::modules::volume=trace,ironbar::clients::volume=trace and capture the full log up until it crashes please? That should hopefully give an indication as to what is happening at the time of crash.

It'd also be good to know if the module functions at all before it crashes. Does it show the right devices/programs and can you change the volume etc?

@JakeStanger commented on GitHub (Sep 5, 2025): I'm going to need some more information for this one, as I run with pipewire-pulse with no issues. Firstly can you confirm it's pipewire-pulse you're using, and could you get a version for that please? Secondly can you run with `IRONBAR_LOG=ironbar::modules::volume=trace,ironbar::clients::volume=trace` and capture the *full* log up until it crashes please? That should hopefully give an indication as to what is happening at the time of crash. It'd also be good to know if the module functions at all before it crashes. Does it show the right devices/programs and can you change the volume etc?

JakeStanger commented

2026-05-22 22:54:32 +01:00

Author

Owner

@bandithedoge commented on GitHub (Sep 5, 2025):

For some reason it stopped doing this after updating to the latest commit and updating my system.

@bandithedoge commented on GitHub (Sep 5, 2025): For some reason it stopped doing this after updating to the latest commit and updating my system.