console-kit-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__INTv()

[Steve Langasek]

No idea what triggered this. c-k-d respawned correctly.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: consolekit 0.4.5-3
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
Date: Sun Sep 2 14:45:50 2012
ExecutablePath: /usr/sbin/console-kit-daemon
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcCmdline: /usr/sbin/console-kit-daemon --no-daemon
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x40ee2e: mov 0x28(%rbx),%rdi
 PC (0x0040ee2e) ok
 source "0x28(%rbx)" (0xaaaaaaaaaaaaaad2) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: consolekit
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__INTv (closure=<optimized out>, return_value=<optimized out>, instance=<optimized out>, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>, param_types=0x1bb2170) at /build/buildd/glib2.0-2.33.10/./gobject/gmarshal.c:410
 _g_closure_invoke_va (closure=0x1bbb620, return_value=0x0, instance=0x1ba8f70, args=0x7fff80d82058, n_params=1, param_types=0x1bb2170) at /build/buildd/glib2.0-2.33.10/./gobject/gclosure.c:840
 g_signal_emit_valist (instance=0x1ba8f70, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fff80d82058) at /build/buildd/glib2.0-2.33.10/./gobject/gsignal.c:3211
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at /build/buildd/glib2.0-2.33.10/./gobject/gsignal.c:3356
Title: console-kit-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__INTv()
UpgradeStatus: Upgraded to quantal on 2012-06-11 (83 days ago)
UserGroups:

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