online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()

[Abdelmalek]

!

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: ubuntu-system-settings-online-accounts 0.7+16.10.20160718-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl wl
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 4 06:13:16 2016
ExecutablePath: /usr/bin/online-accounts-ui
ExecutableTimestamp: 1468844106
InstallationDate: Installed on 2016-07-02 (63 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160701)
ProcCmdline: /usr/bin/online-accounts-ui --socket /run/user/1000/online-accounts-ui/ui-1-ubuntuone --profile unconfined
ProcCwd: /home/qwe
Signal: 6
SourcePackage: ubuntu-system-settings-online-accounts
StacktraceTop:
 QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
 QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
 QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
Title: online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd 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 #1608560, 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.