apport-gtk crashed with signal 5 in g_log_writer_default()

[Hilary Greenhow]

Had just booted ubuntu daily build (previously updated with today's changes) in QEMU/KVM, and then logged on.
I was twidling the VM View menu (i.e.) not doing anything specific with the client system when the error occurred.

ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: apport-gtk 2.26.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
Uname: Linux 6.2.0-18-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 27 14:57:48 2023
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2023-03-23 (3 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230323)
InterpreterPath: /usr/bin/python3.11
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
Signal: 5
SourcePackage: apport
StacktraceTop:
 g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: apport-gtk crashed with signal 5 in g_log_writer_default()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
separator:

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