udisks-daemon crashed with signal 5 in g_udev_marshal_VOID__STRING_OBJECT()

[Henk de Groot]

My system got a problem and asked if I wanted to report it. During the reporting procedure however this error occurred (so it is an error during error reporting).

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: udisks 1.0.4-3ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
CurrentDmesg: [ 160.055921] init: plymouth-stop pre-start process (2626) terminated with status 1
Date: Sun Mar 25 20:36:30 2012
ExecutablePath: /usr/lib/udisks/udisks-daemon
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: FUJITSU SIEMENS LIFEBOOK C Series
ProcCmdline: /usr/lib/udisks/udisks-daemon
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=25e3eb13-22c2-419b-a881-2762192022f7 ro quiet splash vt.handoff=7
Signal: 5
SourcePackage: udisks
Title: udisks-daemon crashed with signal 5 in g_udev_marshal_VOID__STRING_OBJECT()
UpgradeStatus: Upgraded to precise on 2012-03-10 (14 days ago)
UserGroups:

dmi.bios.date: 12/30/2003
dmi.bios.vendor: Insyde/FUJITSU
dmi.bios.version: Version 1.35
dmi.board.name: PI401
dmi.board.vendor: FUJITSU
dmi.board.version: null
dmi.chassis.asset.tag: null
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.chassis.version: null
dmi.modalias: dmi:bvnInsyde/FUJITSU:bvrVersion1.35:bd12/30/2003:svnFUJITSUSIEMENS:pnLIFEBOOKCSeries:pvrnull:rvnFUJITSU:rnPI401:rvrnull:cvnFUJITSU:ct10:cvrnull:
dmi.product.name: LIFEBOOK C Series
dmi.product.version: null
dmi.sys.vendor: FUJITSU SIEMENS

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