kdeinit5 crashed with SIGSEGV in __run_exit_handlers()

[Anna]

kdeinit5 crashed with SIGSEGV in __run_exit_handlers()

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: kinit 5.43.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Tue Mar 13 21:58:38 2018
ExecutablePath: /usr/bin/kdeinit5
InstallationDate: Installed on 2018-03-06 (7 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2)
ProcCmdline: http.so\ [kdeinit5]\ https\ local:/run/user/1000/klauncherTJ1511.1.slave-socket\ local:/run/user/1000/kioclientXM5300.2.slave-socket
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f29ae412ff6 <__run_exit_handlers+294>: mov 0x10(%rax),%rdx
 PC (0x7f29ae412ff6) ok
 source "0x10(%rax)" (0xb0f443b4a0020) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: kinit
StacktraceTop:
 __run_exit_handlers (status=255, listp=0x7f29ae7bb718 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:77
 __GI_exit (status=<optimized out>) at exit.c:139
 KIO::SlaveBase::exit() () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
 KIO::SlaveBase::mimeType(QString const&) () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so
Title: kdeinit5 crashed with SIGSEGV in __run_exit_handlers()
UpgradeStatus: Upgraded to bionic on 2018-03-11 (2 days ago)
UserGroups: adm cdrom dip lpadmin 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 #1542310, 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.