Closed JPyke3 closed 4 years ago
Of course. The old post an issue and resolve it yourself syndrome. In /etc/pulse/client.conf
I had autospawn
set to no
. This has to be set to yes
in order to have it start as part of the c-session scope. Not as a systemd service.
Closing this issue.
Hi All,
Description
I'm not sure if this is an issue with my specific pulse audio config, or if its related to the recent update. But recently my pulseaudio has been crashing whenever I try to run it. The common theme from all the errors is
service-start-limit-hit
but even if i completly kill pulseaudio and try to only start it once, it still reports this error.Things attempted:
Those sweet sweet logs
Below is some pulseaudio info as well as sys info:
pulseaudio --version
pulseaudio -vvvv
systemctl --user status pulseaudio.socket
systemctl --user status pulseaudio.service