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

[ealthuis]

Binary package hint: devicekit-disks

This is a follow up on bug report #469000,

I got a message when trying to mount the Windows XP partition:

Message did not receive a reply (timeout by message bus)

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Nov 1 12:08:01 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/devicekit-disks/devkit-disks-daemon
MachineType: Dell Computer Corporation Dimension 4550
Package: devicekit-disks 007-2ubuntu3
ProcCmdLine: root=UUID=44b0c176-5475-43c6-befb-c00830f407d6 ro quiet splash
ProcCmdline: /usr/lib/devicekit-disks/devkit-disks-daemon
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x26bf4f <g_slice_alloc+15>: call 0x2270f7
 PC (0x0026bf4f) ok
 source "0x2270f7" (0x002270f7) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: devicekit-disks
StacktraceTop:
 g_slice_alloc () from /lib/libglib-2.0.so.0
 g_list_prepend () from /lib/libglib-2.0.so.0
 g_hash_table_get_values () from /lib/libglib-2.0.so.0
 ?? ()
 ?? ()
Title: devkit-disks-daemon crashed with SIGSEGV in g_slice_alloc()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom fuse lpadmin netdev plugdev sambashare scanner
dmi.bios.date: 04/22/2003
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A06
dmi.board.name: 0M0321
dmi.board.vendor: Dell Computer Corp.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: dmi:bvnDellComputerCorporation:bvrA06:bd04/22/2003:svnDellComputerCorporation:pnDimension4550:pvr:rvnDellComputerCorp.:rn0M0321:rvr:cvnDellComputerCorporation:ct6:cvr:
dmi.product.name: Dimension 4550
dmi.sys.vendor: Dell Computer Corporation

[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 #466533, 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.