signon-ui crashed with SIGSEGV in QWindow::setModality()

[Martin Vysny]

I tried to add GTalk IM account but the Google button did nothing and then the crash report popped up.

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: signon-ui-x11 0.17+17.04.20170320-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
Uname: Linux 4.10.0-15-generic x86_64
ApportVersion: 2.20.4-0ubuntu3
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Apr 7 23:08:34 2017
ExecutablePath: /usr/bin/signon-ui
InstallationDate: Installed on 2014-03-07 (1126 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
ProcCmdline: /usr/bin/signon-ui
Signal: 11
SourcePackage: signon-ui
StacktraceTop:
 QWindow::setModality(Qt::WindowModality) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
 ?? ()
 ?? ()
 ?? ()
 QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
Title: signon-ui crashed with SIGSEGV in QWindow::setModality()
UpgradeStatus: Upgraded to zesty on 2017-03-29 (9 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 (thunderbird:2467): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",
 (thunderbird:2467): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",
 (rhythmbox:2464): Rhythmbox-WARNING **: Unable to grab media player keys: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files
 (thunderbird:2456): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",
 (thunderbird:2456): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",

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