udisks-daemon crashed with signal 5 in g_closure_invoke()

[Mario Limonciello]

crashed

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: udisks 1.0.4-3
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu1
Architecture: amd64
CustomUdevRuleFiles: 10-vboxdrv.rules
Date: Thu Mar 8 17:32:22 2012
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-oneiric-amd64-20111017-0
ExecutablePath: /usr/lib/udisks/udisks-daemon
ExecutableTimestamp: 1325679868
InstallationMedia: Ubuntu 11.10 "Oneiric" - Build amd64 LIVE Binary 20111017-03:20
MachineType: Dell Inc. Precision T3600
ProcCmdline: /usr/lib/udisks/udisks-daemon
ProcCwd: /
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=bd5ea84a-e877-4315-87c0-8e4c31714634 ro crashkernel=384M-2G:64M,2G-:128M nomodeset quiet splash vt.handoff=7
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
Title: udisks-daemon crashed with signal 5 in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 05/13/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: X06
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrX06:bd05/13/2011:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct15:cvr:
dmi.product.name: Precision T3600
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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