dbus-daemon crashed with SIGSEGV

Bug #532964 reported by kyleabaker
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: dbus

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu.
Description: Ubuntu lucid (development branch)
Release: 10.04

2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic.
dbus:
  Installed: 1.2.16-2ubuntu3
  Candidate: 1.2.16-2ubuntu3
  Version table:
 *** 1.2.16-2ubuntu3 0
        500 http://us.archive.ubuntu.com lucid/main Packages
        100 /var/lib/dpkg/status

3) What you expected to happen
Not crash

4) What happened instead
Crashed on login

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Fri Mar 5 16:59:04 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /bin/dbus-daemon
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: dbus 1.2.16-2ubuntu3
ProcCmdline: /bin/dbus-daemon --fork --print-pid 5 --print-address 9 --session
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
SegvAnalysis:
 Segfault happened at: 0x7f7a2939bcc9: cmp 0x8(%rax),%r15
 PC (0x7f7a2939bcc9) ok
 source "0x8(%rax)" (0x7f782ac46a38) not located in a known VMA region (needed readable region)!
 destination "%r15" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: dbus
StacktraceTop:
 ?? () from /bin/dbus-daemon
 ?? () from /bin/dbus-daemon
 ?? () from /bin/dbus-daemon
 ?? () from /bin/dbus-daemon
 ?? () from /bin/dbus-daemon
Title: dbus-daemon crashed with SIGSEGV
Uname: Linux 2.6.32-15-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #362565, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
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.