indicator-keyboard-service crashed with SIGSEGV in xkl_config_rec_get_from_server()

[Gatonegro]

This happens randomly: the screen becomes garbled shortly after booting. If I restart manually lightdm from an VT (sudo service lightdm restart) it seems to be fixed -- but this workaround doesn't work for non-technical people.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: indicator-keyboard 0.0.0+14.04.20140227.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
Uname: Linux 3.13.0-14-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.13.2-0ubuntu5
Architecture: i386
Date: Sun Mar 2 21:27:05 2014
ExecutablePath: /usr/lib/i386-linux-gnu/indicator-keyboard-service
InstallationDate: Installed on 2012-09-09 (539 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
ProcCmdline: /usr/lib/i386-linux-gnu/indicator-keyboard-service --use-gtk
ProcEnviron:
 SHELL=/bin/false
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=gl_ES.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb6f429b6: mov 0xc(%esi),%eax
 PC (0xb6f429b6) ok
 source "0xc(%esi)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-keyboard
StacktraceTop:
 ?? () from /usr/lib/libxklavier.so.16
 xkl_config_rec_get_from_server () from /usr/lib/libxklavier.so.16
 lightdm_get_layouts () from /usr/lib/liblightdm-gobject-1.so.0
 lightdm_get_layout () from /usr/lib/liblightdm-gobject-1.so.0
 ?? ()
Title: indicator-keyboard-service crashed with SIGSEGV in xkl_config_rec_get_from_server()
UpgradeStatus: Upgraded to trusty on 2014-02-25 (5 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 #1285534, 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.