gnome-shell crashed with SIGSEGV in meta_context_terminate()

[rajesh]

The error message was generated immediately after login.

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Sat Apr 9 23:20:18 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2022-04-02 (7 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220401)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_IN
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.0-1ubuntu1
SegvAnalysis:
 Segfault happened at: 0x7fb624cbe290 <meta_context_terminate+16>: cmpl $0x4,0x24(%rbx)
 PC (0x7fb624cbe290) ok
 source "$0x4" ok
 destination "0x24(%rbx)" (0xffffffffffffffb4) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 meta_context_terminate () from /lib/x86_64-linux-gnu/libmutter-10.so.0
 ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in meta_context_terminate()
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 #1959937, 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.