You are not logged in.
Hi all, I have a issue about the Pipewire-pulse which is bothering me for a long time.
Every things is fine after booting, but the occurs when I use my PC for a long time without log out or reboot.
When the issue happens, I cannot adjust my volume and cannot play any audio.
And the issue cannot be fixed by
systemctl --user restart wireplumber pipewire pipewire-pulse
, the following error will keep showing. The only way to fix it is log out the user and log back in again.
The following log was capture when the issue occurs.
systemctl --user status pipewire pipewire-pulse
● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
Active: active (running) since Wed 2024-03-20 21:10:09 CST; 3 days ago
TriggeredBy: ● pipewire.socket
Main PID: 86610 (pipewire)
Tasks: 3 (limit: 38207)
Memory: 27.6M (peak: 29.1M)
CPU: 3min 35.987s
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
└─86610 /usr/bin/pipewire
Mar 24 11:18:01 archlinux pipewire[86610]: spa.alsa: front:0p: follower:0 match:0 rate:1.000011 bw:0.128000 thr:256 del:381 target:384 err:-3.000>
Mar 24 11:18:04 archlinux pipewire[86610]: spa.alsa: front:0p: follower:0 match:0 rate:1.000043 bw:0.128000 thr:256 del:380 target:384 err:-4.000>
Mar 24 11:18:07 archlinux pipewire[86610]: spa.alsa: front:0p: follower:0 match:0 rate:1.000030 bw:0.128000 thr:256 del:379 target:384 err:-5.000>
Mar 24 11:18:10 archlinux pipewire[86610]: spa.alsa: front:0p: follower:0 match:0 rate:1.000024 bw:0.128000 thr:256 del:383 target:384 err:-1.000>
Mar 24 11:18:13 archlinux pipewire[86610]: spa.alsa: front:0p: follower:0 match:0 rate:1.000035 bw:0.128000 thr:256 del:382 target:384 err:-2.000>
Mar 24 11:18:16 archlinux pipewire[86610]: spa.alsa: front:0p: follower:0 match:0 rate:1.000026 bw:0.128000 thr:256 del:381 target:384 err:-3.000>
Mar 24 11:18:19 archlinux pipewire[86610]: spa.alsa: front:0p: follower:0 match:0 rate:0.999862 bw:0.128000 thr:256 del:380 target:384 err:-4.000>
Mar 24 11:18:22 archlinux pipewire[86610]: spa.alsa: front:0p: follower:0 match:0 rate:1.000028 bw:0.128000 thr:256 del:384 target:384 err:0.0000>
Mar 24 11:18:25 archlinux pipewire[86610]: spa.alsa: front:0p: follower:0 match:0 rate:0.999974 bw:0.128000 thr:256 del:383 target:384 err:-1.000>
Mar 24 11:18:28 archlinux pipewire[86610]: spa.alsa: front:0p: follower:0 match:0 rate:1.000018 bw:0.128000 thr:256 del:382 target:384 err:-2.000>
● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; enabled; preset: enabled)
Active: active (running) since Wed 2024-03-20 21:10:09 CST; 3 days ago
TriggeredBy: ● pipewire-pulse.socket
Main PID: 86621 (pipewire-pulse)
Tasks: 3 (limit: 38207)
Memory: 75.5M (peak: 78.2M)
CPU: 7min 32.514s
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
└─86621 /usr/bin/pipewire-pulse
Mar 24 11:18:28 archlinux pipewire-pulse[86621]: mod.protocol-pulse: server 0x5f9010f432f0: failed to create client: Connection refused
Mar 24 11:18:28 archlinux pipewire-pulse[86621]: mod.protocol-pulse: server 0x5f9010f432f0: failed to create client: Connection refused
Mar 24 11:18:28 archlinux pipewire-pulse[86621]: mod.protocol-pulse: server 0x5f9010f432f0: failed to create client: Connection refused
Mar 24 11:18:28 archlinux pipewire-pulse[86621]: mod.protocol-pulse: server 0x5f9010f432f0: failed to create client: Connection refused
Mar 24 11:18:28 archlinux pipewire-pulse[86621]: mod.protocol-pulse: server 0x5f9010f432f0: failed to create client: Connection refused
Mar 24 11:18:29 archlinux pipewire-pulse[86621]: mod.protocol-pulse: server 0x5f9010f432f0: failed to create client: Connection refused
Mar 24 11:18:29 archlinux pipewire-pulse[86621]: mod.protocol-pulse: server 0x5f9010f432f0: failed to create client: Connection refused
Mar 24 11:18:29 archlinux pipewire-pulse[86621]: mod.protocol-pulse: server 0x5f9010f432f0: failed to create client: Connection refused
Mar 24 11:18:29 archlinux pipewire-pulse[86621]: mod.protocol-pulse: server 0x5f9010f432f0: failed to create client: Connection refused
Mar 24 11:18:29 archlinux pipewire-pulse[86621]: mod.protocol-pulse: server 0x5f9010f432f0: failed to create client: Connection refused
And
sudo fuser -v /dev/snd/*
USER PID ACCESS COMMAND
/dev/snd/controlC0: hellc 86613 F.... wireplumber
/dev/snd/controlC1: hellc 86613 F.... wireplumber
/dev/snd/seq: hellc 86610 F.... pipewire
pactl info
Connection failure: Connection terminated
pacman -Qs 'pipewire|pulse'
local/gst-plugin-pipewire 1:1.0.3-1
Multimedia graph framework - pipewire plugin
local/gtk-vnc 1.3.1-1
VNC viewer widget for GTK
local/libcanberra 1:0.30+r2+gc0620e4-3
A small and lightweight implementation of the XDG Sound Theme Specification
local/libpipewire 1:1.0.4-1
Low-latency audio/video router and processor - client library
local/libpulse 17.0-3
A featureful, general-purpose sound server (client library)
local/libwireplumber 0.4.17-1
Session / policy manager implementation for PipeWire - client library
local/pipewire 1:1.0.4-1
Low-latency audio/video router and processor
local/pipewire-alsa 1:1.0.3-1
Low-latency audio/video router and processor - ALSA configuration
local/pipewire-audio 1:1.0.3-1
Low-latency audio/video router and processor - Audio support
local/pipewire-jack 1:1.0.3-1
Low-latency audio/video router and processor - JACK replacement
local/pipewire-pulse 1:1.0.4-1
Low-latency audio/video router and processor - PulseAudio replacement
local/wireplumber 0.4.17-1
Session / policy manager implementation for PipeWire
Any help would be much appreciated.
Offline
While unlikely to be directly related your system is in a partially updated state for several of these packages. Do not do that, update your entire system: https://wiki.archlinux.org/title/System … nsupported
More likely to be related there's a systemd-tmpfiles-clean.service and an associated timer that might coincide with the issue and you might have to figure out which file gets cleaned up so that the connection breaks (... alternatively disable the timer so this doesn't run/this might eventually become troublesome if your systemd generates a lot of tmpfiles)
Offline
Thanks your help, I will look at systemd-tmpfiles-clean.service and find out the reason.
Offline