Just after rebooting and logging in, when I started audacious in an xterm, I got a message that it could not connect to PulseAudio, and to make sure that it was running. It was in fact not running. The following errors appear in /var/log/messages: Jul 23 21:14:40 diet-anarchy pulseaudio[2070]: polkit.c: Cannot set UID on session object. Jul 23 21:14:40 diet-anarchy pulseaudio[2070]: main.c: Called SUID root and real-time/high-priority scheduling was requested in the configuration. However, we lack the necessary priviliges: Jul 23 21:14:40 diet-anarchy pulseaudio[2070]: main.c: We are not in group 'pulse-rt' and PolicyKit refuse to grant us priviliges. Dropping SUID again. Jul 23 21:14:40 diet-anarchy pulseaudio[2070]: main.c: For enabling real-time scheduling please acquire the appropriate PolicyKit priviliges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user. Jul 23 21:14:40 diet-anarchy pulseaudio[2070]: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted Jul 23 21:14:40 diet-anarchy pulseaudio[2070]: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted Jul 23 21:15:14 diet-anarchy pulseaudio[2274]: main.c: Called SUID root and real-time/high-priority scheduling was requested in the configuration. However, we lack the necessary priviliges: Jul 23 21:15:14 diet-anarchy pulseaudio[2274]: main.c: We are not in group 'pulse-rt' and PolicyKit refuse to grant us priviliges. Dropping SUID again. Jul 23 21:15:14 diet-anarchy pulseaudio[2274]: main.c: For enabling real-time scheduling please acquire the appropriate PolicyKit priviliges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user. Jul 23 21:15:14 diet-anarchy pulseaudio[2274]: pid.c: Daemon already running. Jul 23 21:15:14 diet-anarchy pulseaudio[2274]: main.c: pa_pid_file_create() failed. I can start pulseaudio as user "beland" and audacious can connect to it, though I do get the following output: N: main.c: Called SUID root and real-time/high-priority scheduling was requested in the configuration. However, we lack the necessary priviliges: N: main.c: We are not in group 'pulse-rt' and PolicyKit refuse to grant us priviliges. Dropping SUID again. N: main.c: For enabling real-time scheduling please acquire the appropriate PolicyKit priviliges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user. W: pid.c: Stale PID file, overwriting. W: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted W: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0 ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0 This is with pulseaudio-0.9.10-1.fc9.i386. This didn't used to be a problem with Fedora 9, though I did install some updates today.
Probably a duplicate of bug #438284 or bug #444684.
An xterm? PA is being started in GNOME and KDE sessions only right. If you neither PA will not be running and your applications will not be able to find it.
I do have a Gnome session, inside of which I have started gnome-terminal from the graphical menu.
Please check ~/.xsession-errors for an PA or ESD related output. Have you played around with the "start ESD" checkbox in gnome-sound-properties or in GConf? They need to be *enabled*.
Also, have you seen the two bugs Andre linked? Are they relevant to you, do they apply to your case?
I don't see a "start ESD" checkbox in gnome-sound-properties. I haven't experienced this problem recently, and I rebooted twice today. Perhaps the fixes pushed for those other bugs has cured this problem. Thanks!