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

[psl]

Binary package hint: devicekit-disks

Nothing special to report. Ubuntu runs from LiveCD and I do install to /dev/sda10. I see a bug report. Just a test install.

ProblemType: Crash
.etc.fstab:
 aufs / aufs rw 0 0
 tmpfs /tmp tmpfs nosuid,nodev 0 0
 /dev/sda6 swap swap defaults 0 0
Architecture: i386
Date: Wed Oct 28 16:17:22 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/devicekit-disks/devkit-disks-daemon
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091027)
Package: devicekit-disks 007-2ubuntu3
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: 0xfe0f1d <dbus_g_method_return_error+29>: mov 0x10(%esi),%edi
 PC (0x00fe0f1d) ok
 source "0x10(%esi)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%edi" 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 i686
UserGroups:

dmi.bios.date: 11/25/2002
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: 6.00 PG
dmi.board.name: SiS-745
dmi.chassis.type: 3
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvr6.00PG:bd11/25/2002:svn:pn:pvr:rvn:rnSiS-745:rvr:cvn:ct3:cvr:

[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.