Description of problem: After upgrading to version 0.3.26 of pipewire, sound stopped working. Version-Release number of selected component (if applicable): 0.3.26 & 0.3.25 How reproducible: always Steps to Reproduce: 1. upgrade pipewire pipewire-alsa pipewire-gstreamer pipewire-jack-audio-connection-kit pipewire-libs pipewire-pulseaudio pipewire-utils to 0.3.26-4 2. reboot/login Actual results: No sound, running journalctl --since today --user-unit pipewire shows: -- Boot d36f0d53a1234139b87fdc0aca6eb8d7 -- May 04 05:42:58 redacted.example.com systemd[1634]: Started Multimedia Service. May 04 05:43:23 redacted.example.com pipewire-media-session[1914]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply May 04 06:49:47 redacted.example.com pipewire-media-session[1914]: no node found for 51 May 04 06:50:05 redacted.example.com pipewire-media-session[1914]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply May 04 06:50:08 redacted.example.com pipewire-media-session[1914]: no node found for 50 May 04 06:50:33 redacted.example.com pipewire-media-session[1914]: no node found for 50 May 04 06:50:35 redacted.example.com pipewire-media-session[1914]: no node found for 50 <repeated> ... Expected results: After downgrading to 0.3.25-4 journalctl shows: -- Boot 80c19edc82724e9f98fa587260303f2f -- May 04 07:39:17 redacted.example.com systemd[1618]: Started Multimedia Service. May 04 07:39:42 redacted.example.com pipewire-media-session[1902]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply May 04 07:45:34 redacted.example.com pipewire-media-session[1902]: device 'alsa_card.pci-0000_00_03.0': can't restore profile: No such device and sound works again. Additional info:
Some things to check: - check if there are any .rpmnew config files in /etc/pipewire/ and /etc/pipewire/media-session.d/ - attach the output of pw-dump >dump.log here - run: killall -9 pipewire-media-session PIPEWIRE_DEBUG=3 pipewire-media-session 2>session.log And attach the session.log file here.
Well, this is frustrating. After re-upgrading it just works :-(. - check if there are any .rpmnew config files in /etc/pipewire/ and /etc/pipewire/media-session.d/ there are not. - attach the output of pw-dump >dump.log here - run: killall -9 pipewire-media-session PIPEWIRE_DEBUG=3 pipewire-media-session 2>session.log And attach the session.log file here. will do so after posting this comment. Not sure if that's useful now that the issue disappeared?
Created attachment 1779438 [details] pw-dump >dump.log
Created attachment 1779443 [details] pipewire-media-session 2>session.log
OK, after trying that, the sound disappeared again. I'll attach the changed output of dump.log and do the pipewire-media-session again...
Created attachment 1779446 [details] pw-dump >dump2.log
Created attachment 1779447 [details] pipewire-media-session 2>session2.log
And now (with the PIPEWIRE_DEBUG=3 pipewire-media-session 2>session2.log) running, I have sound again.
Not sure what was fixed, but upgrading to pipewire-0.3.27-1 this PM made my sound work again without the kill/restart work-around.
Sorry for hijacking this ticket. When I log out of F34 GNOME Shell and log back in, sound is not available anymore. Rebooting fixes it for now, but only until I log out and back in. This is with 0.3.27 and a fully updated F34. Seems to have been introduced recently.
So, after logging out, there are three processes still running for the user: pipewire, pipewire-pulse, pipewire-media-session When logging in again, I need to kill them, and they get respawned and make sound work.
Just FYI, I do not see the problem that Michael Schwendt describes. My sound works fine with the latest version.
Is it considered allowable for me to close this? I'm now at pipewire-0.3.29 and everything seems to work just fine for my configuration. Happy to close it if that is allowed.
Ok, closing. thanks for testing.