Comment 23 for bug 933209

Yes, that's helpful. This one seems to be the first sign of failure:

> dbus[625]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out

Without consolekit, PulseAudio won't have access to sound cards.

Second, this:

> pulseaudio[1075]: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to
> autolaunch a dbus-daemon without a $DISPLAY for X11

It looks like pulseaudio is first being started inside a console, or some other context that can't access X.

I'm really not an expert on the consolekit/dBus stuff, but it looks like PulseAudio is not the primary source of failure here.

> I noted that pulseaudio is started by 106 on startup, is this normal?

It would be normal to have it started by lightdm at startup, but I don't know if this is the same as "106".