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

[Josh Blair]

Simply trying to add online accounts in Kubuntu 17.10

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: signon-ui-x11 0.17+17.10.20170606-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
Uname: Linux 4.13.0-16-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Oct 20 11:21:22 2017
ExecutablePath: /usr/bin/signon-ui
InstallationDate: Installed on 2017-09-18 (31 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/signon-ui
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f54c5cfe5a0 <_ZN7QWindow11setModalityEN2Qt14WindowModalityE>: mov 0x8(%rdi),%rax
 PC (0x7f54c5cfe5a0) ok
 source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
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 artful on 2017-10-20 (0 days ago)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
XsessionErrors:
 (kerneloops-applet:2014): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",
 (kerneloops-applet:2014): 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 #1723230, 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.