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

[michalzuber]

Binary package hint: devicekit-disks

I was installing Karmic Koala AMD64 RC on a USB pendrive and the crash report appeared.

ProblemType: Crash
.etc.fstab:
 aufs / aufs rw 0 0
 tmpfs /tmp tmpfs nosuid,nodev 0 0
 /dev/sda4 swap swap defaults 0 0
Architecture: amd64
Date: Sun Oct 25 17:22:53 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: LENOVO 2746AEG
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: 0x7f79be34407e <dbus_g_method_return_error+14>: mov 0x20(%rdi),%r8d
 PC (0x7f79be34407e) 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: 12/25/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 6AET53WW
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: 2746AEG
dmi.board.vendor: LENOVO
dmi.board.version: LENOVO 6AET53WW
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: LENOVO 6AET53WW
dmi.modalias: dmi:bvnLENOVO:bvr6AET53WW:bd12/25/2008:svnLENOVO:pn2746AEG:pvrThinkPadSL:rvnLENOVO:rn2746AEG:rvrLENOVO6AET53WW:cvnLENOVO:ct10:cvrLENOVO6AET53WW:
dmi.product.name: 2746AEG
dmi.product.version: ThinkPad SL
dmi.sys.vendor: LENOVO

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