installing 9.10 rc

[Don]

Binary package hint: devicekit-disks

still in live cd portion of install.

ProblemType: Crash
.etc.fstab:
 aufs / aufs rw 0 0
 tmpfs /tmp tmpfs nosuid,nodev 0 0
Architecture: i386
Date: Tue Oct 27 12:33:34 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/devicekit-disks/devkit-disks-daemon
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
MachineType: IBM 2668B1U
Package: devicekit-disks 007-2ubuntu2
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
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: 0x119f1d <dbus_g_method_return_error+29>: mov 0x10(%esi),%edi
 PC (0x00119f1d) 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: 09/15/2005
dmi.bios.vendor: IBM
dmi.bios.version: 1YET58WW (1.23 )
dmi.board.name: 2668B1U
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr1YET58WW(1.23):bd09/15/2005:svnIBM:pn2668B1U:pvrThinkPadT43:rvnIBM:rn2668B1U:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 2668B1U
dmi.product.version: ThinkPad T43
dmi.sys.vendor: IBM

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