apport-gtk crashed with SIGSEGV in g_type_create_instance()

[anthonykour]

apport-gtk crashed with SIGSEGV in g_type_create_instance()

ProblemType: Crash
DistroRelease: Ubuntu 22.10
Package: apport-gtk 2.23.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CrashReports:
 640:1000:125:56970220:2022-09-07 19:23:07.273167371 -0400:2022-09-07 19:23:08.273167371 -0400:/var/crash/_usr_bin_gnome-shell.1000.crash
 640:1000:125:8037568:2022-09-07 19:23:09.737195968 -0400:2022-09-07 19:23:10.737195968 -0400:/var/crash/_usr_share_apport_apport-gtk.1000.crash
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 7 19:23:08 2022
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2022-09-04 (3 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
InterpreterPath: /usr/bin/python3.10
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1
PythonDetails: N/A
SegvAnalysis:
 Segfault happened at: 0x7f600578bc04: mov 0x18(%rax),%rax
 PC (0x7f600578bc04) ok
 source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: apport
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.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
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: apport-gtk crashed with SIGSEGV in g_type_create_instance()
UpgradeStatus: Upgraded to kinetic on 2022-09-07 (0 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
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 #1988982, 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.