udisks-daemon crashed with signal 5 in g_udev_marshal_VOID__STRING_OBJECT()

[Shibli]

udisks-daemon crashed with signal 5 in g_udev_marshal_VOID__STRING_OBJECT()

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: udisks 1.0.4-1
ProcVersionSignature: Ubuntu 3.0.0-15.24-generic 3.0.13
Uname: Linux 3.0.0-15-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Wed Dec 17 10:28:16 2008
ExecutablePath: /usr/lib/udisks/udisks-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: Hewlett-Packard HP Compaq 6530b (GW688AV)
ProcCmdline: /usr/lib/udisks/udisks-daemon
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-15-generic root=UUID=1ba4108c-e35d-45d5-9c64-3d4d085486bf ro vga=769 quiet splash vt.handoff=7
Signal: 5
SourcePackage: udisks
StacktraceTop:
 ?? ()
 ?? ()
 g_udev_marshal_VOID__STRING_OBJECT () from /usr/lib/i386-linux-gnu/libgudev-1.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: udisks-daemon crashed with signal 5 in g_udev_marshal_VOID__STRING_OBJECT()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 09/14/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PDD Ver. F.11
dmi.board.name: 30DD
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 96.20
dmi.chassis.asset.tag: CNU9405C11
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDDVer.F.11:bd09/14/2009:svnHewlett-Packard:pnHPCompaq6530b(GW688AV):pvrF.11:rvnHewlett-Packard:rn30DD:rvrKBCVersion96.20:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6530b (GW688AV)
dmi.product.version: F.11
dmi.sys.vendor: Hewlett-Packard

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #899757, 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.