signon-ui crashed with SIGSEGV in QObject::event()

[Dahna]

Running 13.10 daily build downloaded today (no updates available, seems the latest version)
Signon-ui crashes almost any time if I do something less straightforward then to enter login/pass within 5-10 seconds.
For example if I forgot a password and try several variants, click links, going back to all settings or just minimize it (for example to remember a password via browser)
If I success to enter password from the first attempts - no problems

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: signon-ui 0.15daily13.06.25-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Sat Sep 7 02:24:28 2013
ExecutablePath: /usr/bin/signon-ui
MarkForUpload: True
ProcCmdline: /usr/bin/signon-ui
SegvAnalysis:
 Segfault happened at: 0x7f8feb1358cb: mov 0x28(%rdi),%r12d
 PC (0x7f8feb1358cb) ok
 source "0x28(%rdi)" (0x00000028) not located in a known VMA region (needed readable region)!
 destination "%r12d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: signon-ui
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
 QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
Title: signon-ui crashed with SIGSEGV in QObject::event()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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