apport-gtk crashed with SIGABRT in g_assertion_message()

[BobDodds]

dpkg -a configure on upgrade

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: apport-gtk 2.20.7-0ubuntu2
Uname: Linux 4.13.0-041300rc1-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CrashCounter: 1
CrashReports:
 640:1000:119:2330704:2017-10-10 12:04:35.859253406 -0400:2017-10-10 12:04:36.859253406 -0400:/var/crash/_usr_bin_nautilus-desktop.1000.crash
 640:1000:119:2037487:2017-10-10 12:05:33.015285491 -0400:2017-10-10 12:05:34.015285491 -0400:/var/crash/_usr_lib_gnome-terminal_gnome-terminal-server.1000.crash
 640:1000:119:23910688:2017-10-10 12:11:48.858009099 -0400:2017-10-10 12:11:49.858009099 -0400:/var/crash/_usr_share_apport_apport-gtk.1000.crash
CurrentDesktop: GNOME
Date: Tue Oct 10 12:11:33 2017
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2017-07-23 (79 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
InterpreterPath: /usr/bin/python3.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
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
Signal: 6
SourcePackage: apport
StacktraceTop:
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: apport-gtk crashed with SIGABRT in g_assertion_message()
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 #1622414, 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.