Bug 1954504 - No sound after logout/login with own userid
Summary: No sound after logout/login with own userid
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pipewire
Version: 34
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Wim Taymans
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-28 09:44 UTC by Klaus Siebke
Modified: 2021-05-23 08:38 UTC (History)
6 users (show)

Fixed In Version: pipewire-0.3.27-1.fc34 pipewire-0.3.28-1.fc34
Clone Of:
: 1981944 (view as bug list)
Environment:
Last Closed: 2021-05-20 01:12:23 UTC
Type: Bug
Embargoed:
copr: needinfo-
ksiebke: needinfo-


Attachments (Terms of Use)

Description Klaus Siebke 2021-04-28 09:44:12 UTC
Description of problem:

After logout with the own userid and logging in right afterwards the sound is not available.
Only after a complete reboot the sound is back again

Version-Release number of selected component (if applicable):

Fedora Version 34 (MATE-Compiz) 64-bit
Kernel Linux 5.11.15-300.fc34.x86_64 x86_64
pipewire 0.3.26
(all current versions from 2021/04/28)

How reproducible:


Steps to Reproduce:
1. logout with own userid
2. login again


Actual results:

No Sound

Expected results:

Sound should be available again

Additional info:


a) Messages from pipewire during logout

Apr 28 09:27:29 fedora rtkit-daemon[852]: Successfully made thread 1407 of process 1407 (/usr/bin/pipewire) owned by '1000' high priority at nice level -11.
Apr 28 09:27:29 fedora rtkit-daemon[852]: Successfully made thread 1411 of process 1411 (/usr/bin/pipewire-pulse) owned by '1000' high priority at nice level -11.
Apr 28 09:27:29 fedora rtkit-daemon[852]: Successfully made thread 1416 of process 1407 (/usr/bin/pipewire) owned by '1000' RT at priority 20.
Apr 28 09:27:29 fedora rtkit-daemon[852]: Successfully made thread 1424 of process 1424 (/usr/bin/pipewire-media-session) owned by '1000' high priority at nice level -11.
Apr 28 09:27:29 fedora rtkit-daemon[852]: Successfully made thread 1415 of process 1411 (/usr/bin/pipewire-pulse) owned by '1000' RT at priority 20.
Apr 28 09:27:29 fedora rtkit-daemon[852]: Successfully made thread 1429 of process 1424 (/usr/bin/pipewire-media-session) owned by '1000' RT at priority 20.
Apr 28 09:27:36 fedora systemd[1084]: pipewire-pulse.socket: Deactivated successfully.
Apr 28 09:27:36 fedora systemd[1084]: pipewire.socket: Deactivated successfully.
Apr 28 09:33:28 fedora systemd[3721]: pipewire-pulse.socket: Deactivated successfully.
Apr 28 09:33:28 fedora systemd[3721]: pipewire.socket: Deactivated successfully.

b) Messages from pipewire when logging in again:

Apr 28 09:33:38 fedora pipewire-media-session[1424]: no node found for 43
Apr 28 09:33:38 fedora pipewire-pulse[1411]: stream 0x55e88378d7a0: error no node available

Comment 1 Giuseppe Castagna 2021-04-28 14:42:19 UTC
This looks as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1954517 (or viceversa)

Comment 2 copr 2021-04-28 14:52:22 UTC
I believe these are instead all duplicates of https://bugzilla.redhat.com/show_bug.cgi?id=1943867

I can confirm restarting pipewire-pulse works for me

Comment 3 Giuseppe Castagna 2021-04-28 15:11:49 UTC
@copr it indeed looks as a duplicate of the https://bugzilla.redhat.com/show_bug.cgi?id=1943867. However the solution proposed there does not work since I checked /usr/lib/systemd/user/pipewire-pulse.service and it already contains the lines

Wants=pipewire.service
After=pipewire.service

Comment 4 Giuseppe Castagna 2021-04-28 15:24:38 UTC
... and restarting *just* pipewire-pulse does not work for me. I have to restart both pipewire and then pipewire-pulse to have the sound working again.

Comment 5 Klaus Siebke 2021-04-28 17:03:27 UTC
I can confirm that my /usr/lib/systemd/user/pipewire-pulse.service also contains the two additional lines 

Wants=pipewire.service
After=pipewire.service

in the [Unit] section.

(I mentioned above that I am using the latest version of FC34) 

However the bug still persists.

Comment 6 Fedora Update System 2021-05-06 09:37:05 UTC
FEDORA-2021-41bc11dd99 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-41bc11dd99

Comment 7 Fedora Update System 2021-05-07 01:03:36 UTC
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.

Comment 8 Klaus Siebke 2021-05-10 09:43:56 UTC
Sorry, but even with the latest pipewire version (pipewire-0.3.27-1.fc34 ) the error is still present.

Just to explain why the bug needs to be fixed:

From time to time I need to logout and login again to refresh some user settings and after logging in the sound system is broken.
So I cannot use my messaging system until I reboot my machine ...
In FC32 which I used before I had no issues.

Comment 9 Giuseppe Castagna 2021-05-10 09:49:48 UTC
I confirm that the problem is still present. See also https://bugzilla.redhat.com/show_bug.cgi?id=1954517#c4 for more details.

@ksiebke you do not need to reboot. It should suffice to do 

systemctl --user restart pipewire pipewire-pulse

and you should be able to use audio again (at least, it works for me)

Comment 10 Fedora Update System 2021-05-19 08:48:03 UTC
FEDORA-2021-28d7b1f215 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-28d7b1f215

Comment 11 Giuseppe Castagna 2021-05-19 19:08:40 UTC
The latest bodhi update fixed the bug. Thanks a lot!

pipewire0.2-libs-0.2.7-5.fc34.x86_64
pipewire-libs-0.3.28-1.fc34.x86_64
pipewire-0.3.28-1.fc34.x86_64
pipewire-alsa-0.3.28-1.fc34.x86_64
pipewire-gstreamer-0.3.28-1.fc34.x86_64
pipewire-jack-audio-connection-kit-0.3.28-1.fc34.x86_64
pipewire-pulseaudio-0.3.28-1.fc34.x86_64
pipewire-utils-0.3.28-1.fc34.x86_64

Comment 12 Fedora Update System 2021-05-20 01:12:23 UTC
FEDORA-2021-28d7b1f215 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Klaus Siebke 2021-05-21 08:30:55 UTC
I just installed the regular update and it works now.
Thank you for your support!


Note You need to log in before you can comment on or make changes to this bug.