d3Xt3r, 8 months ago Does restarting PipeWire fix it? systemctl --user restart pipewire.service or systemctl --user restart wireplumber pipewire pipewire-pulse If that works, you could create a systemd unit file to automatically run that after resume. <span style="color:#323232;">[Unit] </span><span style="color:#323232;">Description=Restart Pipewire after resume </span><span style="color:#323232;">After=suspend.target </span><span style="color:#323232;"> </span><span style="color:#323232;">[Service] </span><span style="color:#323232;">Type=simple </span><span style="color:#323232;">ExecStart=/usr/bin/systemctl --user restart pipewire.service </span><span style="color:#323232;"> </span><span style="color:#323232;">[Install] </span><span style="color:#323232;">WantedBy=suspend.target </span>
Does restarting PipeWire fix it?
systemctl --user restart pipewire.service
or
systemctl --user restart wireplumber pipewire pipewire-pulse
If that works, you could create a systemd unit file to automatically run that after resume.
<span style="color:#323232;">[Unit] </span><span style="color:#323232;">Description=Restart Pipewire after resume </span><span style="color:#323232;">After=suspend.target </span><span style="color:#323232;"> </span><span style="color:#323232;">[Service] </span><span style="color:#323232;">Type=simple </span><span style="color:#323232;">ExecStart=/usr/bin/systemctl --user restart pipewire.service </span><span style="color:#323232;"> </span><span style="color:#323232;">[Install] </span><span style="color:#323232;">WantedBy=suspend.target </span>