udisks-daemon crashed with signal 5 in g_closure_invoke()

[Tobias Quinn]

Happens a minute after login from fresh start

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
ApportVersion: 1.94-0ubuntu2
Architecture: amd64
CurrentDmesg: [ 33.021044] wlan0: no IPv6 routers present
CustomUdevRuleFiles: 98-buspirate.rules 50-brainaudio.rules
Date: Tue Mar 6 16:34:25 2012
ExecutablePath: /usr/lib/udisks/udisks-daemon
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
MachineType: LENOVO 1068E7G
ProcCmdline: /usr/lib/udisks/udisks-daemon
ProcEnviron:

ProcKernelCmdLine: root=UUID=2112c57a-12db-4c1f-9e5c-a6f44af36e46 ro crashkernel=384M-2G:64M,2G-:128M 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
 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: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 02/22/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 44CN28WW
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Emerald Lake
dmi.board.vendor: LENOVO
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnLENOVO:bvr44CN28WW:bd02/22/2011:svnLENOVO:pn1068E7G:pvrLenovoB570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
dmi.product.name: 1068E7G
dmi.product.version: Lenovo B570
dmi.sys.vendor: LENOVO

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