kdeconnectd crashed with SIGSEGV in Device::privateReceivedPackage()

[Stanley C Slomberg]

I do not know why it crashed, have no idea

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: kdeconnect 1.2.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Apr 9 17:35:55 2018
ExecutablePath: /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd
InstallationDate: Installed on 2017-12-23 (107 days ago)
InstallationMedia: Kubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcCmdline: /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f817b3af9a8: mov 0x10(%r13),%rdi
 PC (0x7f817b3af9a8) ok
 source "0x10(%r13)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kdeconnect
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kdeconnect/kdeconnect_notifications.so
 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kdeconnect/kdeconnect_notifications.so
 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kdeconnect/kdeconnect_notifications.so
 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kdeconnect/kdeconnect_notifications.so
 Device::privateReceivedPackage(NetworkPackage const&) () from /usr/lib/x86_64-linux-gnu/libkdeconnectcore.so.1
Title: kdeconnectd crashed with SIGSEGV in Device::privateReceivedPackage()
UpgradeStatus: No upgrade log present (probably fresh install)
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 #1746580, 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.