cairo-dock crashed with SIGSEGV in dbus_connection_dispatch()

Bug #1033690 reported by Bill Risch
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cairo-dock (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Crash while attempting to log out

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: cairo-dock-core 3.0.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
Uname: Linux 3.5.0-8-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
CrashCounter: 1
Date: Mon Aug 6 16:59:49 2012
ExecutablePath: /usr/bin/cairo-dock
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120511)
ProcCmdline: cairo-dock
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f505a20b800: mov (%rdi),%rax
 PC (0x7f505a20b800) ok
 source "(%rdi)" (0x00000009) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cairo-dock
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
Title: cairo-dock crashed with SIGSEGV in dbus_connection_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 gnome-session[1884]: WARNING: Error while executing session-migration: Failed to execute child process "session-migration" (No such file or directory)
 gnome-session[1884]: WARNING: Could not parse desktop file /home/bill/.config/autostart/xfce4-settings-helper-autostart.desktop: Key file does not have key 'Name'
 gnome-session[1884]: WARNING: could not read /home/bill/.config/autostart/xfce4-settings-helper-autostart.desktop

Revision history for this message
Bill Risch (brisch) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () from /tmp/tmp_dvilh/lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /tmp/tmp_dvilh/lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /tmp/tmp_dvilh/lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_connection_dispatch () from /tmp/tmp_dvilh/lib/x86_64-linux-gnu/libdbus-1.so.3
 message_queue_dispatch (source=source@entry=0xf384b0, callback=<optimized out>, user_data=<optimized out>) at dbus-gmain.c:90

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in cairo-dock (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libgdk-pixbuf2.0-common version 2.26.1-1ubuntu1 required, but 2.26.2-0ubuntu1 is available
libgdk-pixbuf2.0-0 version 2.26.1-1ubuntu1 required, but 2.26.2-0ubuntu1 is available
outdated debug symbol package for libgdk-pixbuf2.0-0: package version 2.26.2-0ubuntu1 dbgsym version 2.26.1-1ubuntu1
libcups2 version 1.6.0-0bzr1 required, but 1.6.1-0ubuntu1 is available
outdated debug symbol package for libgdk-pixbuf2.0-0: package version 2.26.2-0ubuntu1 dbgsym version 2.26.1-1ubuntu1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.