onboard crashed with SIGSEGV in PyObject_Call()

[Cary]

Crashed when trying to log in. The onscreen keyboard was on the login screen, but not being used.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: onboard 0.99.0~alpha1~tr1190-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Sun Jul 14 11:51:06 2013
ExecutablePath: /usr/bin/onboard
InstallationDate: Installed on 2013-07-01 (12 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130630)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/bin/onboard --xid
SegvAnalysis:
 Segfault happened at: 0x5714bb <PyObject_CallObject+235>: mov 0x18(%rdi),%esi
 PC (0x005714bb) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: onboard
StacktraceTop:
 PyObject_Call (kw=0x0, arg=(), func=<method at remote 0x7fad865c32d8>) at ../Objects/abstract.c:2082
 PyEval_CallObjectWithKeywords (kw=0x0, arg=(), func=<method at remote 0x7fad865c32d8>) at ../Python/ceval.c:3947
 PyObject_CallObject (o=<method at remote 0x7fad865c32d8>, a=<optimized out>) at ../Objects/abstract.c:2072
 ?? () from /usr/lib/python3/dist-packages/Onboard/osk.cpython-33m-x86_64-linux-gnu.so
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: onboard crashed with SIGSEGV in PyObject_Call()
UpgradeStatus: No upgrade log present (probably fresh install)
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 #1195857, 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.