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

[McDope]

Tried to re-add a google account after deleting it (got oauth errors with gmail notifier extension)

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: signon-ui 0.15daily13.06.12-0ubuntu1 [modified: usr/bin/signon-ui usr/bin/tst_inactivity_timer]
ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
Uname: Linux 3.10.0-4-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Sun Jul 21 09:38:00 2013
ExecutablePath: /usr/bin/signon-ui
InstallationDate: Installed on 2010-05-06 (1171 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MarkForUpload: True
ProcCmdline: /usr/bin/signon-ui
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, user)
 LANGUAGE=de_DE:en
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fcb076748cb: mov 0x28(%rdi),%r12d
 PC (0x7fcb076748cb) 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: Upgraded to saucy on 2013-07-06 (14 days ago)
UserGroups: adm admin audio cdrom dialout dip disk fax floppy fuse libvirtd lpadmin netdev plugdev sambashare saned tape users vboxusers video

[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.