After sleep + resume + logging in, audio is not working. The journalctl output shows:
Oct 24 10:23:08 qaa pipewire-pulse[2054]: mod.protocol-pulse: 0x56325495e770: failed to connect client: Host is down Oct 24 10:23:08 qaa pipewire-pulse[2054]: mod.protocol-pulse: client 0x5632549861b0 [PulseAudio Volume Control]: ERROR command:9 (SET_CLIENT_NAME) tag:1 error:6 (Host is down) Oct 24 10:23:09 qaa pipewire-pulse[2054]: mod.protocol-pulse: 0x56325495e770: failed to connect client: Host is down Oct 24 10:23:09 qaa pipewire-pulse[2054]: mod.protocol-pulse: client 0x563254985cb0 [PulseAudio Volume Control]: ERROR command:9 (SET_CLIENT_NAME) tag:1 error:6 (Host is down) Oct 24 10:23:10 qaa pipewire-pulse[2054]: mod.protocol-pulse: 0x56325495e770: failed to connect client: Host is down Oct 24 10:23:10 qaa pipewire-pulse[2054]: mod.protocol-pulse: client 0x563254dab930 [PulseAudio Volume Control]: ERROR command:9 (SET_CLIENT_NAME) tag:1 error:6 (Host is down) Oct 24 10:23:11 qaa pipewire-pulse[2054]: mod.protocol-pulse: 0x56325495e770: failed to connect client: Host is down Oct 24 10:23:11 qaa pipewire-pulse[2054]: mod.protocol-pulse: client 0x56325496be00 [PulseAudio Volume Control]: ERROR command:9 (SET_CLIENT_NAME) tag:1 error:6 (Host is down) Oct 24 10:23:12 qaa pipewire-pulse[2054]: mod.protocol-pulse: 0x56325495e770: failed to connect client: Host is down Oct 24 10:23:12 qaa pipewire-pulse[2054]: mod.protocol-pulse: client 0x563254985cb0 [PulseAudio Volume Control]: ERROR command:9 (SET_CLIENT_NAME) tag:1 error:6 (Host is down) [...] Oct 24 10:23:28 qaa pipewire-pulse[2054]: mod.protocol-pulse: 0x56325495e770: failed to connect client: Host is down Oct 24 10:23:28 qaa pipewire-pulse[2054]: mod.protocol-pulse: client 0x563254dab930 [PulseAudio Volume Control]: ERROR command:9 (SET_CLIENT_NAME) tag:1 error:6 (Host is down) Oct 24 10:23:29 qaa pipewire-pulse[2054]: mod.protocol-pulse: 0x56325495e770: failed to connect client: Host is down Oct 24 10:23:29 qaa pipewire-pulse[2054]: mod.protocol-pulse: client 0x563254dab930 [PulseAudio Volume Control]: ERROR command:9 (SET_CLIENT_NAME) tag:1 error:6 (Host is down) Oct 24 10:23:32 qaa pipewire-pulse[2054]: mod.protocol-pulse: 0x56325495e770: failed to connect client: Host is down Oct 24 10:23:32 qaa pipewire-pulse[2054]: mod.protocol-pulse: client 0x563254dab930 [Firefox]: ERROR command:9 (SET_CLIENT_NAME) tag:1 error:6 (Host is down) Oct 24 10:23:32 qaa pipewire-pulse[2054]: mod.protocol-pulse: 0x56325495e770: failed to connect client: Host is down Oct 24 10:23:32 qaa pipewire-pulse[2054]: mod.protocol-pulse: client 0x563254dab930 [ALSA plug-in [firefox]]: ERROR command:9 (SET_CLIENT_NAME) tag:1 error:6 (Host is down) Oct 24 10:23:32 qaa pipewire-pulse[2054]: mod.protocol-pulse: 0x56325495e770: failed to connect client: Host is down Oct 24 10:23:32 qaa pipewire-pulse[2054]: mod.protocol-pulse: client 0x563254dab930 [ALSA plug-in [firefox]]: ERROR command:9 (SET_CLIENT_NAME) tag:1 error:6 (Host is down) Some context: Normally, when I log in, journalctl shows something like Oct 16 02:58:49 qaa lightdm[1928]: pam_unix(lightdm:session): session opened for user vinc17(uid=1000) by vinc17(uid=0) Oct 16 02:58:49 qaa systemd[1]: Created slice user-1000.slice - User Slice of UID 1000. Oct 16 02:58:49 qaa systemd[1]: Starting [email protected] - User Runtime Directory /run/user/1000... Oct 16 02:58:49 qaa systemd-logind[1330]: New session '2' of user 'vinc17' with class 'user' and type 'x11'. Oct 16 02:58:49 qaa systemd[1826]: Reached target sound.target - Sound Card. Oct 16 02:58:49 qaa systemd[1]: Finished [email protected] - User Runtime Directory /run/user/1000. Oct 16 02:58:49 qaa systemd[1]: Starting [email protected] - User Manager for UID 1000... Oct 16 02:58:49 qaa (systemd)[2026]: pam_unix(systemd-user:session): session opened for user vinc17(uid=1000) by vinc17(uid=0) Oct 16 02:58:49 qaa systemd-logind[1330]: New session '3' of user 'vinc17' with class 'manager' and type 'unspecified'. Oct 16 02:58:49 qaa systemd[2026]: Queued start job for default target default.target. [...] and then various services are started (like pipewire-pulse). But after logging out + sleep + resume + logging in (because I moved my laptop to another place): Oct 24 10:20:33 qaa lightdm[1047466]: pam_unix(lightdm:session): session opened for user vinc17(uid=1000) by vinc17(uid=0) Oct 24 10:20:33 qaa systemd-logind[1330]: New session '1822' of user 'vinc17' with class 'user' and type 'x11'. Oct 24 10:20:33 qaa wpa_supplicant[1429]: wlp0s20f3: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25 Oct 24 10:20:33 qaa wpa_supplicant[1429]: wlp0s20f3: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected Oct 24 10:20:33 qaa systemd[1]: Started session-1822.scope - Session 1822 of User vinc17. Oct 24 10:20:33 qaa lightdm[1047604]: gkr-pam: couldn't run gnome-keyring-daemon: No such file or directory Oct 24 10:20:33 qaa lightdm[1047466]: gkr-pam: gnome-keyring-daemon didn't start properly Oct 24 10:20:33 qaa lightdm[1047466]: Failed to write utmpx: No such file or directory Oct 24 10:20:33 qaa ModemManager[1421]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.3': not supported by any plugin [wpa_supplicant errors due to a certificate issue] and no services are started. In particular, audio isn't working at all. It seems that the user-1000.slice unit from the previous login session was not removed as I can see about it: Oct 24 09:01:17 qaa systemd[1]: user-1000.slice: Unit now frozen-by-parent. Oct 24 10:20:29 qaa systemd[1]: user-1000.slice: Unit now thawed. Any idea? -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
