gnome-shell crashed with SIGSEGV in __GI_getenv()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Crash happened upon boot.
I don't know if it is related, but touchpad gestures don't work in this startup.
ProblemType: Crash
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.0-1ubuntu1
ProcVersionSign
Uname: Linux 5.19.0-19-generic x86_64
ApportVersion: 2.23.1-0ubuntu1
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Oct 8 18:00:37 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/
GsettingsChanges:
InstallationDate: Installed on 2022-02-02 (248 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=es_AR:es
PATH=(custom, no user)
XDG_RUNTIME_
LANG=es_AR.UTF-8
SHELL=/bin/false
RelatedPackageV
SegvAnalysis:
Segfault happened at: 0x7fb4b7c3f0fd <__GI_getenv+173>: cmp (%rbx),%r12w
PC (0x7fb4b7c3f0fd) ok
source "(%rbx)" (0x55a863020cf9) 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=0x7fb4b4f
() at /lib/x86_
() at /lib/x86_
udev_device_
g_udev_
Title: gnome-shell crashed with SIGSEGV in __GI_getenv()
UpgradeStatus: Upgraded to kinetic on 2022-09-29 (9 days ago)
UserGroups: N/A
separator:
| Nicolás Abel Carbone (nicocarbone) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
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.