Created attachment 1801996 [details]
Description of problem:
After upgrade pipewire to 0.3.31-4.fc35 version all audio devices disappeared
Last not affected by this issue version is 0.3.31-3.fc35
Created attachment 1801997 [details]
Created attachment 1801998 [details]
pw-cli ls Node
Created attachment 1801999 [details]
gnome control center - Sound
There is no session manager started, I believe f35 being updated to enable either pipewire-media-session or wireplumber, depending on what is installed.
Removing ~/.config/pipewire/media-session.d and starting pipewire-media-session manually fixes the issue for me as a workaround.
In Fedora 35 you need to manually enable and start the session manager:
systemctl --user enable pipewire-media-session
systemctl --user start pipewire-media-session
Or you can now also switch to WirePlumber. AFAIK, the defaults are being updated to enable the services by default
but maybe that is not active for you yet.
(In reply to Wim Taymans from comment #6)
> In Fedora 35 you need to manually enable and start the session manager:
> systemctl --user enable pipewire-media-session
> systemctl --user start pipewire-media-session
> Or you can now also switch to WirePlumber. AFAIK, the defaults are being
> updated to enable the services by default
> but maybe that is not active for you yet.
[mikhail@fedora ~]$ systemctl --user enable pipewire-media-session
Created symlink /home/mikhail/.config/systemd/user/pipewire.service.wants/pipewire-media-session.service → /usr/lib/systemd/user/pipewire-media-session.service.
[mikhail@fedora ~]$ systemctl --user start pipewire-media-session
Yes it helped, but why pipewire-media-session did not enabled by default after update?
Even update to 0.3.32-1.fc35.x86_64 didn't enable this service.
> Yes it helped, but why pipewire-media-session did not enabled by default after update?
Maybe the fedora-release-35 package was not the most recent version?
(In reply to Wim Taymans from comment #8)
> Maybe the fedora-release-35 package was not the most recent version?
# rpm -qa | grep fedora-release
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle.
Changing version to 35.
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version'
to a later Fedora Linux version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora Linux 35 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.
Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.
If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.
If you are unable to reopen this bug, please file a new report against an
Thank you for reporting this bug and we are sorry it could not be fixed.