devkit-disks-daemon crashed with SIGSEGV in dbus_g_method_return_error()

[Tom Pino]

Binary package hint: devicekit-disks

This occured on the LiveCD for the RC.

Have no idea what it is about. No noticable effect. Install has just finished fine and I am about to reboot.

ProblemType: Crash
.etc.fstab:
 aufs / aufs rw 0 0
 tmpfs /tmp tmpfs nosuid,nodev 0 0
 /dev/sda5 swap swap defaults 0 0
 /dev/sdb5 swap swap defaults 0 0
Architecture: amd64
Date: Thu Oct 22 19:21:29 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/devicekit-disks/devkit-disks-daemon
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.3)
MachineType: Dell Inc. Dell XPS420
Package: devicekit-disks 007-2ubuntu2
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --
ProcCmdline: /usr/lib/devicekit-disks/devkit-disks-daemon
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x7f188149307e <dbus_g_method_return_error+14>: mov 0x20(%rdi),%r8d
 PC (0x7f188149307e) ok
 source "0x20(%rdi)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%r8d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: devicekit-disks
StacktraceTop:
 dbus_g_method_return_error ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: devkit-disks-daemon crashed with SIGSEGV in dbus_g_method_return_error()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups:

dmi.bios.date: 03/27/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0TP406
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/27/2008:svnDellInc.:pnDellXPS420:pvr:rvnDellInc.:rn0TP406:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: Dell XPS420
dmi.sys.vendor: Dell Inc.

[Apport retracing service (apport)]

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 #452208, 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.