Description of problem: When I login for the first time the output devices (laptop tigerlake internal speakers and dell monitor soundbar for output, internal mike and logitech brio webcam for input) are there. Music plays perfectly and I can switch from one device to another without any problem. If I logout (gdm) and login TO THE SAME ACCOUNT then the output devices have desappeared. The point is that the processes of the previous session have not been killed, they are still there beppe 28398 0.0 0.0 325780 12700 ? S<sl 11:50 0:00 /usr/bin/pipewire beppe 28418 0.0 0.0 317376 11740 ? S<l 11:50 0:00 /usr/bin/pipewire-media-session beppe 28701 0.1 0.0 319176 14624 ? S<sl 11:50 0:00 /usr/bin/pipewire-pulse It suffices to kill pipewire and pipewire-pulse and the devices reappear and work as expected (since two new processes have been respawned). Notice that this does not happens when I login in a different account (the old pipewire processes are correctly killed) Version-Release number of selected component (if applicable): I have a fresh installation of Fedora 34 pipewire0.2-libs-0.2.7-5.fc34.x86_64 pipewire-0.3.26-1.fc34.x86_64 pipewire-libs-0.3.26-1.fc34.x86_64 pipewire-pulseaudio-0.3.26-1.fc34.x86_64 How reproducible: Steps to Reproduce: 1. Login via gdm: devices are there (check the pipewire process numbers) 2. Logout 3. Login to the same account: devices are no longer there (but the pipewire process still are) 4. Kill pipe-wire and pipewire-pulseaudio (or start a new pipewire process): devices are there again
Just updated to pipewire-0.3.26-3 and the problem persists
It looks like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1954504
FEDORA-2021-41bc11dd99 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-41bc11dd99
Just installed the update from koji: pipewire0.2-libs-0.2.7-5.fc34.x86_64 pipewire-libs-0.3.27-1.fc34.x86_64 pipewire-0.3.27-1.fc34.x86_64 pipewire-alsa-0.3.27-1.fc34.x86_64 pipewire-gstreamer-0.3.27-1.fc34.x86_64 pipewire-jack-audio-connection-kit-0.3.27-1.fc34.x86_64 pipewire-pulseaudio-0.3.27-1.fc34.x86_64 pipewire-utils-0.3.27-1.fc34.x86_64 unfortunately it does not fix the problem of this bug report. I have exactly the same behavior as before. Logging out and then logging in *the same* account does not kill the pipewire processes and this makes the audio devices not accessible. Logging out and then logging in a different account does not present this problem since new user processes are spawned. There is however an improvement over the previous version since the random crashes of audio devices (actually of pipewire-media-session) at the start of a new session no longer happen.
FEDORA-2021-41bc11dd99 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
(In reply to Fedora Update System from comment #5) > FEDORA-2021-41bc11dd99 has been pushed to the Fedora 34 stable repository. > If problem still persists, please make note of it in this bug report. I did it! See the previous post
The new update of pipewire does not fix the problem pipewire0.2-libs-0.2.7-5.fc34.x86_64 pipewire-libs-0.3.27-2.fc34.x86_64 pipewire-0.3.27-2.fc34.x86_64 pipewire-alsa-0.3.27-2.fc34.x86_64 pipewire-gstreamer-0.3.27-2.fc34.x86_64 pipewire-jack-audio-connection-kit-0.3.27-2.fc34.x86_64 pipewire-pulseaudio-0.3.27-2.fc34.x86_64 pipewire-utils-0.3.27-2.fc34.x86_64 again: I have exactly the same behavior as before. Logging out and then logging in **the same** account does not kill the pipewire processes and this makes the audio devices not accessible. Logging out and then logging in a different account does not present this problem since new user processes are spawned. After loggin-in the second time a systemctl --user restart pipewire pipewire-pulse fixes the problem