WirePlumber integration doesn't handle PipeWire/WirePlumber restart

[misuzu]

When I restart PipeWire (journalctl --user -u pipewire.service) the WirePlumber integration stops working without logging anything.

It also says segmentation fault on ^C:

^C[2024-02-03 10:11:42.019] [info] Quitting.
^C[1]    10856 segmentation fault (core dumped) 

Here's my waybar config:

{
    "layer": "top",
    "position": "top",
    "height": 24,

    "modules-left": ["hyprland/workspaces"],
    "modules-center": ["hyprland/window"],
    "modules-right": ["network", "memory", "wireplumber", "battery", "clock", "tray"],
    "clock": {
        "format": "{:%a %b %d %T}",
        "interval": 1,
        "tooltip": false
    },
    "memory": {
        "interval": 30,
        "format": "RAM: {used:0.2f} / {total:0.2f} GiB",
        "tooltip": false
    },
    "wireplumber": {
        "format": "VOL: {volume}% {icon}",
        "format-bluetooth": "{volume}% {icon}",
        "scroll-step": 2,
        "on-click": "pavucontrol",
        "tooltip": false
    },
    "network": {
        "interface": "wlp1s0",
        "format": "D: {bandwidthDownBytes}, U: {bandwidthUpBytes}",
        "interval": 1
    },
    "battery": {
        "format": "BAT: {capacity}%",
    },
    "tray": {
        "icon-size": 16
    }
}

% waybar -v    
Waybar v0.9.24

[fxzzi]

Is this also possibly related to my issue which is that the wireplumber module sometimes doesn't work when I first login to hyprland? I have to restart waybar for the module to show properly (otherwise it's stuck on 0%)

[RamyFerhat59]

I have the exact same problem on described by @Fxzzi

[megalinee]

I have the same issue as @Fxzzi and @RamyFerhat59 . I autologin to arch and start Hyprland on a launch script within getty so I'm assuming the quick start isn't giving enough time for wireplumber to start.

[rtgiskard]

+1

[megalinee]

If you change the pipewire default device after starting waybar it fixes the issue. I just put pactl set-default-sink <default-device> to execute after waybar automatically and the issue is gone.

[Myned]

An alternative solution I currently use is simply to start waybar slightly delayed after Hyprland starts with:

exec-once = sleep 1 && waybar

If home-manager, programs.waybar.systemd.enable should be disabled with this to prevent conflicts.