Description of problem:
There is no default daemon to manage pulseaudio, and it has problems when is
started as systemwide as root, so I could not use an init script for that,
because it must be started as the user. I sould start it everytime I login to X.
Version-Release number of selected component (if applicable):
Just install the OS.
No daemon present.
A daemon starting pulseaudio.
Is this related to my report at:
I see problems in KDE with audio - and in /var/log/messages I get a line:
Nov 9 17:41:21 lapmike2 pulseaudio: main.c: This program is not intended
to be run as root (unless --system is specified).
Yes, you or that program or script running pulseaudio is running that as root
and must send --system switch to pulseaudio. But the problem is that even if you
send that switch to pulseaudio it does not start and in some experiments it was
seen that even if it starts, clients from users can not connect to that, and so
the user must start it manually as user.
In Fedora PulseAudio is started as a session daemon.
If you want to start PulseAudio as system wide daemon than you have to manually
create an init script and set up a few things like an access group 'pulse-access'.
Please note that it is not recommended to start PA as system daemon. If you do
it, than you are expected to know pretty well what you are doing. In most cases
running PA as system daemon is *not* what you want. The only use case where this
might make sense is on thin clients where no local user exists.
I will close this bug now, since PA is run as a session daemon on Fedora.
Note that as a consequence running all sound through PA, a session daemon, sound
for a Fedora system is now broken by default unless a user is using a X session
which is already set up to start PA (ie, gnome, kde). Someone running a
different window manager, or heaven forbid, trying to work in a text console, is
toast unless they go learn how to run PA themselves (something I'm just now
Rather than being tied to a high-level Xwindows session manager, shouldn't PA be
started by default at login along with the other local, userspace device
wrangling which happens when someone logs in on console rather than remotely?
Which is a process that appears to have changed a great deal since I last looked
at it, so I've no useful specific suggestions right now, but I could open a new
bugzilla entry to work on it.
"No sound for you" (unless you're using gnome or kde) seems a rather draconian
default. Sound is something which, having no graphical component, should work
in runlevel 3, but currently does not.