apport-gtk crashed with SIGABRT in g_assertion_message_error()

[BertN45]

The system crashed during the update of the virtualbox guest addition drivers during the system upgrade from 4.17.0-7 to 4.17.0-9

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: apport-gtk 2.20.10-0ubuntu9
ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12
Uname: Linux 4.17.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
CrashReports:
 640:1000:118:7015528:2018-08-29 17:59:46.687878370 -0400:2018-08-29 17:59:47.687878370 -0400:/var/crash/_usr_bin_rhythmbox.1000.crash
 640:1000:118:17562022:2018-08-29 18:00:31.657382249 -0400:2018-08-29 18:00:32.657382249 -0400:/var/crash/_usr_share_apport_apport-gtk.1000.crash
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 29 18:00:23 2018
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2018-06-05 (85 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180603)
InterpreterPath: /usr/bin/python3.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
Python3Details: /usr/bin/python3.6, Python 3.6.6+, python3-minimal, 3.6.6-1
PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3
Signal: 6
SourcePackage: apport
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_error () from /usr/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_error()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf

[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 #1756469, 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.