On Sun, Nov 22, 2009 at 1:26 PM, Filofel <email address hidden> wrote:
> I see the pulseaudio messages in the log (the one below is from the latest / current boot), but I see no pulseaudio process in ps when I'm using the machine.
> So it seems pulseaudio was active in the machine at boot, 14 seconds after the very first boot-time log message was written, but isn't when I look at it.
Oh, that's gdm, then, which uses PA (as the gdm user) for login
"ready" alert. Once you've logged in as your user, you can probably
verify with "pgrep pulseaudio" that it is not running as your user.
On Sun, Nov 22, 2009 at 1:26 PM, Filofel <email address hidden> wrote:
> I see the pulseaudio messages in the log (the one below is from the latest / current boot), but I see no pulseaudio process in ps when I'm using the machine.
> So it seems pulseaudio was active in the machine at boot, 14 seconds after the very first boot-time log message was written, but isn't when I look at it.
Oh, that's gdm, then, which uses PA (as the gdm user) for login
"ready" alert. Once you've logged in as your user, you can probably
verify with "pgrep pulseaudio" that it is not running as your user.