apport-gtk crashed with SIGSEGV in g_type_create_instance()

[Raymond Kimathi]

Dash To Panel

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: apport-gtk 2.20.11-0ubuntu79
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CrashReports:
 640:1000:124:11380649:2022-03-18 01:21:03.894274711 +0300:2022-03-18 01:21:04.894274711 +0300:/var/crash/_usr_bin_gjs-console.1000.crash
 640:1000:124:7279496:2022-03-18 01:21:06.638510227 +0300:2022-03-18 01:21:07.638510227 +0300:/var/crash/_usr_share_apport_apport-gtk.1000.crash
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 18 01:21:05 2022
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2022-03-17 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220316)
InterpreterPath: /usr/bin/python3.10
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 3.10.1-0ubuntu2
PythonDetails: /usr/bin/python3.10, Python 3.10.3, python-is-python3, 3.9.2-2
SegvAnalysis:
 Segfault happened at: 0x7f7d19f63cf4: mov 0x18(%rax),%rax
 PC (0x7f7d19f63cf4) 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: No upgrade log present (probably fresh install)
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 #1945114, 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.