udisks-daemon crashed with signal 5 in g_udev_marshal_VOID__STRING_OBJECT()

[Ehcor8]

By closing video player Xine on ub 12.04 i386 on HP dv7 dual core T6600 4 Gb ram

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: udisks 1.0.4-3ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12
Uname: Linux 3.2.0-20-generic-pae i686
NonfreeKernelModules: wl fglrx
ApportVersion: 1.95-0ubuntu1
Architecture: i386
CustomUdevRuleFiles: 10-vboxdrv.rules
Date: Sat Mar 24 00:02:03 2012
ExecutablePath: /usr/lib/udisks/udisks-daemon
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120322)
MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
ProcCmdline: /usr/lib/udisks/udisks-daemon
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic-pae root=UUID=211fbe9a-046a-45c0-9202-431f74addd4e 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: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 08/25/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.46
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3624
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 18.51
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnHewlett-Packard:rn3624:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv7 Notebook PC
dmi.product.version: Rev 1
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.