lightdm crashed with SIGSEGV in g_closure_invoke()

[Francesco Fumanti]

I get this error message shortly after logging into oneiric precise.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: lightdm 1.0.6-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-3.9-generic 3.2.0-rc4
Uname: Linux 3.2.0-3-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Dec 13 11:31:55 2011
ExecutablePath: /usr/sbin/lightdm
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: lightdm
ProcEnviron: PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x411138: mov 0x28(%rax),%ecx
 PC (0x00411138) ok
 source "0x28(%rax)" (0xaaaaaaaaaaaaaad2) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: lightdm
StacktraceTop:
 ?? ()
 g_closure_invoke (closure=0x656a80, return_value=0x0, n_param_values=1, param_values=0x664100, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.31.4.is.2.31.2/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=<optimized out>, emission_return=0x0, instance_and_params=0x664100) at /build/buildd/glib2.0-2.31.4.is.2.31.2/./gobject/gsignal.c:3302
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=0x7fff02302898) at /build/buildd/glib2.0-2.31.4.is.2.31.2/./gobject/gsignal.c:3033
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at /build/buildd/glib2.0-2.31.4.is.2.31.2/./gobject/gsignal.c:3090
Title: lightdm crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to precise on 2011-12-09 (3 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 #902698, 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.

[Francesco Fumanti (frafu)]

It might be also relevant to know that I am using the onscreen keyboard and that I have enabled the hover click by the hover buttons provided by the onscreen keyboard.

(On a side note: The fact, that the onscreen keyboard has buttons to enable the hover click (automatic click) does not make the bug #810711 a11y: add option to start dwelling obsolete. In fact, a user that can only use dwell clicking has no way to get to the onscreen keyboard as long as the options menu is not dwellable.)