Red Hat Bugzilla – Bug 830406
"User-configured server refusing to start/autospawn"
Last modified: 2012-08-12 16:24:27 EDT
Description of problem:
pulseaudio rarely if ever autospawns since I upgraded to F17, so I have to start it manually. It regularly shuts down, as well, so I have to keep restarting it myself.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot up
2. ps -Afl|grep pulseaudio
ps shows that pulseaudio is not running
pulseaudio should be running
It seems to be shutting down when I start it normally due to:
I: [pulseaudio] core.c: We are idle, quitting...
I: [pulseaudio] main.c: Daemon shutdown initiated.
I guess this is normal.
I don't know if this is relevant, but when I start it manually for the first time, it tends to start with the output device muted, but the relevant mute control is not visible in kmix, only in pavucontrol.
Exit on idle is normal behaviour but it should restart when requested.
You can cp /etc/pulse/daemon.conf $HOME/.oulse and edit exit-idle-time if you really want to keep it running. You can also change your log-levels and redirect to syslog. man pulse-deamon.conf for details
Just to make sure you don't have autospawn = no in you ~/.pulse/client.conf?
that is $HOME/.pulse
Thanks for the hints, Brendan. This was actually caused by an old file in ~/.pulse that was last modified last year. No idea what created it. When I deleted that file, this issue went away.
I have the same problem with an F16/F17 system (and a pure F17 system nearby). Erase the ~/.pulse directory and no change. No autospawn... ever. What in the world *signals* to not autospawn. What is the "user-configured server" flag??
autospawn = yes
daemon-binary = /usr/bin/pulseaudio
extra-arguments = --log-target=syslog
high-priority = yes
nice-level = -11
realtime-scheduling = yes
realtime-priority = 5
rlimit-nice = 31
rlimit-rtprio = 9
rlimit-rttime = 1000000