Summary: | Pulseaudio 6.0 crashes upon starting up | ||
---|---|---|---|
Product: | PulseAudio | Reporter: | guido |
Component: | daemon | Assignee: | pulseaudio-bugs |
Status: | RESOLVED NOTABUG | QA Contact: | pulseaudio-bugs |
Severity: | normal | ||
Priority: | medium | CC: | lennart |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
guido
2015-02-15 16:29:25 UTC
Hi, Is it the client or the PulseAudio server that crashes? Would it be possible for you to attach a backtrace? Thanks. It probably exits cleanly, so I suppose there is no backtrace. If you start PulseAudio with gdb, gdb will break on this crash because there is a SIGABRT signal. At that point, if you run "bt full" you will get a backtrace, which is what I'm looking for here. Can you do that? Thanks in advance. It's not a bug. I think it was due to the fact that X was not running... I found other error messages that explain the above: Feb 17 11:28:29 vortex pulseaudio[6696]: [pulseaudio] module-jackdbus-detect.c: Unable to contact D-Bus session bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 Feb 17 11:28:29 vortex pulseaudio[6696]: [pulseaudio] module.c: Failed to load module "module-jackdbus-detect" (argument: "channels=2"): initialization failed. Feb 17 11:28:29 vortex pulseaudio[6696]: [pulseaudio] main.c: Module load failed. Feb 17 11:28:29 vortex pulseaudio[6696]: [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 Feb 17 11:28:29 vortex pulseaudio[6696]: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 And X was not running due to the fact that gnome-settings-daemon had not been linked yet against the new pulseaudio. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.