apport-gtk crashed with SIGSEGV

[Rune Nordblom]

Logged into Ubuntu 17.10 after upgrading.

Received this messages right away.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: apport-gtk 2.20.7-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.10.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashReports:
 640:1000:118:7071255:2017-10-20 11:58:57.119010448 +0200:2017-10-20 11:58:58.119010448 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
 664:1000:118:0:2017-10-20 13:27:44.683255171 +0200:2017-10-20 13:27:44.683255171 +0200:/var/crash/_usr_share_skypeforlinux_skypeforlinux.1000.upload
 640:1000:118:1761472:2017-10-20 13:27:43.595255851 +0200:2017-10-20 13:27:44.595255851 +0200:/var/crash/_usr_share_skypeforlinux_skypeforlinux.1000.crash
CurrentDesktop: Unity:Unity7
Date: Fri Oct 20 11:58:52 2017
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2016-02-13 (615 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
InterpreterPath: /usr/bin/python3.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
SegvAnalysis:
 Segfault happened at: 0x7f108a1120a9: mov (%rbx),%rdi
 PC (0x7f108a1120a9) ok
 source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: apport
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: apport-gtk crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-10-20 (0 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 #1552577, 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.