Description of problem:
If you log out and log back in to your GNOME session, suddenly no sound card is available. That has unpleasant consequences. Not only you can't play any sound, but also apps trying to play a sound either wait/hang indefinitely (e.g. a youtube video in firefox spins forever, can't play just the video without audio) or crash (virt-manager did that, IIRC).
In order to trigger this, just log out and log back in without any wait time. You'll see no audio icon in the top right corner, and no audio devices present in gnome-control-center -> Sound. See the screenshot.
If I replace wireplumber with pipewire-media-session, the problem is gone.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install clean F35 Workstation, set up a user
2. log in, see the audio icon in top right
3. log out
4. log in again
5. see no audio icon in top right, see no audio devices in gnome-control-center->Sound, see app issues when trying to play a sound or touch the audio device in general
6. sudo dnf swap wireplumber pipewire-media-session
8. repeat the steps, see no issues this time
Waiting for 30+ seconds in gdm before another login avoids this bug, it seems.
Also, this bug doesn't seem to be triggered when you change users, instead of relogging as the same user.
Created attachment 1829353 [details]
missing audio devices due to this bug
Created attachment 1829354 [details]
Created attachment 1829355 [details]
system journal after triggering the bug
Proposing as a Final blocker:
"The installed system must be able to play back sound with gstreamer-based applications. "
"Shutting down, rebooting, logging in and logging out must work using standard console commands and the mechanisms offered (if any) by all release-blocking desktops. "
"Logging in must transfer the user from the login screen/prompt to their working environment, and logging out must return the user to the environment from which they logged in, working as expected. "
This doesn't work as expected (as the criterion says). Relogging without a delay is also quite a common scenario, I think (that's how I found this). Quirks in gnome-shell sometimes make you to relog. Gnome-shell extensions updates ask you to relog. Changing your user groups needs you to relog. And switching between a Wayland and X11 session also requires you to relog (that was my case to spot this).
+3 in https://pagure.io/fedora-qa/blocker-review/issue/499 , marking accepted.
FEDORA-2021-b70755fdc3 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-b70755fdc3
I can confirm that the latest update (comment #6) fixes the issue. The sound works after multiple log outs and log ins.
FEDORA-2021-b70755fdc3 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.
I can also confirm this is fixed.
Might be related and still exists: bug #2012848