udisks-daemon crashed with signal 5 in g_closure_invoke()

[Paul]

Crash occurred while computer was unattended; no further details.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: udisks 1.0.4-3
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
Date: Sat Mar 3 21:14:54 2012
ExecutablePath: /usr/lib/udisks/udisks-daemon
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
MachineType: Acer Aspire 1810T
ProcCmdline: /usr/lib/udisks/udisks-daemon
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic root=UUID=46b09540-36ca-47ef-9c67-240a87a35845 ro quiet splash vt.handoff=7 pcie_aspm=force i8042.reset
Signal: 5
SourcePackage: udisks
StacktraceTop:
 ?? ()
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: udisks-daemon crashed with signal 5 in g_closure_invoke()
UpgradeStatus: Upgraded to precise on 2012-01-24 (39 days ago)
UserGroups:

dmi.bios.date: 08/31/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: v1.3314
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JM11-MS
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810T:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: Aspire 1810T
dmi.product.version: v1.3314
dmi.sys.vendor: Acer

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