udisks-daemon crashed with signal 5 in g_closure_invoke()

[Matthew Wynn]

I believe this happened right after I was making an Ubuntu Onieric boot USB from Precise. It claimed to have finished successfully.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: udisks 1.0.4-3
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: fglrx wl
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CustomUdevRuleFiles: z80_user.rules
Date: Mon Mar 12 13:39:43 2012
ExecutablePath: /usr/lib/udisks/udisks-daemon
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
MachineType: Dell Inc. Inspiron 1764
ProcCmdline: /usr/lib/udisks/udisks-daemon
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=97919f0a-3798-4fb0-8fa4-cf8ae190bc57 ro 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: Upgraded to precise on 2012-03-11 (1 days ago)
UserGroups:

dmi.bios.date: 03/29/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 0H4K11
dmi.board.vendor: Dell Inc.
dmi.board.version: A13
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A13
dmi.modalias: dmi:bvnDellInc.:bvrA13:bd03/29/2011:svnDellInc.:pnInspiron1764:pvrA13:rvnDellInc.:rn0H4K11:rvrA13:cvnDellInc.:ct8:cvrA13:
dmi.product.name: Inspiron 1764
dmi.product.version: A13
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.