signon-ui crashed with SIGABRT in QMessageLogger::fatal()

[Alan]

Crash after update.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: signon-ui 0.15+13.10.20131003.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic i686
ApportVersion: 2.12.5-0ubuntu1
Architecture: i386
Date: Mon Oct 7 18:53:33 2013
ExecutablePath: /usr/bin/signon-ui
InstallationDate: Installed on 2013-06-19 (110 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
MarkForUpload: True
ProcCmdline: /usr/bin/signon-ui
Signal: 6
SourcePackage: signon-ui
StacktraceTop:
 QMessageLogger::fatal(char const*, ...) const () from /usr/lib/i386-linux-gnu/libQt5Core.so.5
 ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so
 ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so
 ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so
 ?? () from /usr/lib/i386-linux-gnu/libQt5Gui.so.5
Title: signon-ui crashed with SIGABRT in QMessageLogger::fatal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev robots sambashare sudo vboxusers

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

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[f(fanta) (fanta)]

I reproduce the bug every time after booting the machine, as soon as I log on, with ubuntu 14.10.