gnome-shell crashed with SIGSEGV in __GI_getenv()

Bug #1991402 reported by Khairul Aizat Kamarudzzaman
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
New
Undecided
Unassigned

Bug Description

sudden crashed

ProblemType: Crash
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-17.17-generic 5.19.7
Uname: Linux 5.19.0-17-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME-Greeter:GNOME
Date: Fri Sep 30 22:57:16 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2020-06-25 (826 days ago)
InstallationMedia:

JournalErrors: -- No entries --
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 43.0-1ubuntu1
SegvAnalysis:
 Segfault happened at: 0x7f2b3f03f0fd <__GI_getenv+173>: cmp (%rbx),%r12w
 PC (0x7f2b3f03f0fd) ok
 source "(%rbx)" (0x55841e15ef1b) not located in a known VMA region (needed readable region)!
 destination "%r12w" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 __GI_getenv (name=0x7f2b3c34c43b "STEMD_DEVICE_VERIFY_SYSFS") at ./stdlib/getenv.c:84
 ?? () from /lib/x86_64-linux-gnu/libudev.so.1
 ?? () from /lib/x86_64-linux-gnu/libudev.so.1
 ?? () from /lib/x86_64-linux-gnu/libudev.so.1
 ?? () from /lib/x86_64-linux-gnu/libudev.so.1
Title: gnome-shell crashed with SIGSEGV in __GI_getenv()
UpgradeStatus: Upgraded to kinetic on 2022-04-25 (157 days ago)
UserGroups: N/A
separator:

Revision history for this message
Khairul Aizat Kamarudzzaman (fenris) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1990000, 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.

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.