Pulseaudio crashes quite often

[LCID Fire]

Binary package hint: pulseaudio

After the last updates on Jaunty (around 2009-02-17) Pulseaudio does no longer start or crashes quite often.

[Ryan Kitty (gothickitty93)]

do any of the other sound servers work? (OSS or ALSA)

[LCID Fire (lcid-fire)]

I haven't tested OSS but Alsa works. Normally I would not even complain but it seems to me like you did remove alsas dmix configuration which now results in only one app being able to use the soundcard.

[Ryan Kitty (gothickitty93)]

Ok, we're going to need someone else to look into this bug, because I'm not really that techy about sound systems in Ubuntu. Sorry if I caused any confusion, because I was just curious if the others worked.

[Daniel T Chen (crimsun)]

By default, the pulseaudio daemon is not configured to run as a system-wide process. I added comments to /etc/init.d/pulseaudio specifically to address the confusion.

For further debugging, I presume you will not be using system-wide invocation but per-user GNOME session invocation.

Because I enabled autospawn, the daemon will die due to ALSA bugs, currently; we're tracking them on alsa-devel.

Please attach a log (pulseaudio -k ; pulseaudio -vv) of your user's invocation of the daemon from the command line until it appears to crash.

[LCID Fire (lcid-fire)]

Ok, today pulseaudio did at least start up - but nevertheless crashes after some time.
What I'm wondering is:
Why isn't apport catching the pulseaudio crash?
Why isn't there any pulseaudio log written (since it's a user process instead of /var/log it could be written to /tmp/log or something)?
Why is there no attemt to restart pulseaudio?
Why do the -k -vv options not output to stdout?