You are not logged in.
I have a laptop always connected to an external display via HDMI, and set my system (through the KDE Plasma System Settings) to output sound to the display speakers. After a some package updates which included the pipewire package (0.3.33), at boot I always find the default sound output set to the laptop speakers; I've tried setting it back to the HDMI output, via the system tray and also using the pactl set-default-sink command, which switches the output correctly, but after a reboot the settings are back to the laptop speakers output.
I've noticed that, after a reboot, the ~/.config/pipewire/media-session.d/default-nodes file always contains just '{ }', and it changes to
{
"default.configured.audio.sink": { "name": "alsa_output.pci-0000_04_00.1.hdmi-stereo" }
}
after I set the audio output manually to HDMI. I can't figure out what's causing this, though...
Last edited by ITA84 (2021-08-08 13:43:13)
Offline
I have the exact same problem. Every time pipewire.service starts / restarts the default-nodes reset to '{ }'. Very recent update I suppose?
It might have something to do with this commit: https://gitlab.freedesktop.org/pipewire … 5d22ce1eaa but I'm not sure.
It's something that has appeared after the latest update for me (so running pipewire version 0.3.33)
Edit:
After compiling version 0.3.32 on my own machine, I can safely say, that this issue wasn't there in that version of PipeWire.
I'm looking more into the bug and will update when I figure something out.
Edit 2:
Can confirm that it it the commit that I'm referring to, that breaks default sink / source... Everything before that commit works just fine, everything after resets the default-nodes file.
Last edited by peterkmoss (2021-08-07 20:35:53)
Offline
Same here, default device changed since the latest update.
Last edited by Kindred (2021-08-07 22:49:53)
Offline
I've commented on the commit on Gitlab, so you guys can follow along there: https://gitlab.freedesktop.org/pipewire … 5d22ce1eaa
Thankfully W. Taymans is very active on the project!
Offline
Thanks a lot for your help!
Offline
Okay just for info, the issue seems to be fixed in master of PipeWire, so next release, which should come relatively soon I assume, will have the issue fixed. The PR is merged (https://gitlab.freedesktop.org/pipewire … quests/869), so it's only a matter of time before the next release version.
For now we'll have to live with it - or if you're impatient you could install it from source I'll just stick to the repositories.
Also big thanks to pvir, for fixing the issue so fast!
Last edited by peterkmoss (2021-08-08 13:29:30)
Offline