gnome-shell crashed with SIGSEGV in __GI_getenv("MESSAGES_DEBUG") from [g_getenv() from] should_drop_message()

Bug #2027830 reported by Cliff Carson
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
New
Medium
Unassigned

Bug Description

New install today. Tested switching to another user on this system which was successful but when I switch back this crash was waithing.

ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: gnome-shell 44.3-1ubuntu1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
ApportVersion: 2.26.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME-Greeter:GNOME
Date: Fri Jul 14 14:58:47 2023
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2023-07-14 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230712.1)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/false
 XDG_RUNTIME_DIR=<set>
RelatedPackageVersions: mutter-common 44.3-1ubuntu1
SegvAnalysis:
 Segfault happened at: 0x7f8686e3f95d <__GI_getenv+173>: cmp (%rbx),%r12w
 PC (0x7f8686e3f95d) ok
 source "(%rbx)" (0x37970fcf9c425fae) 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=0x7f86877a93e7 "MESSAGES_DEBUG") at ./stdlib/getenv.c:84
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_writer_default () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ()
 g_log_structured_array () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in __GI_getenv()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
separator:

Revision history for this message
Cliff Carson (ccarson1) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __GI_getenv (name=0x7f86877a93e7 "MESSAGES_DEBUG") at ./stdlib/getenv.c:84
 should_drop_message (log_level=log_level@entry=G_LOG_LEVEL_DEBUG, log_domain=log_domain@entry=0x0, fields=fields@entry=0x7f86417f8820, n_fields=n_fields@entry=6) at ../../../glib/gmessages.c:2649
 g_log_writer_default (log_level=log_level@entry=G_LOG_LEVEL_DEBUG, fields=fields@entry=0x7f86417f8820, n_fields=n_fields@entry=6, user_data=0x0) at ../../../glib/gmessages.c:2764
 default_log_writer (log_level=G_LOG_LEVEL_DEBUG, fields=0x7f86417f8820, n_fields=6, user_data=<optimized out>) at ../src/main.c:403
 g_log_structured_array (n_fields=6, fields=0x7f86417f8820, log_level=G_LOG_LEVEL_DEBUG) at ../../../glib/gmessages.c:1983

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Daniel van Vugt (vanvugt) wrote (last edit ): Re: gnome-shell crashed with SIGSEGV in __GI_getenv()

It looks like the gnome-shell process has a corrupt __environ block causing getenv() to crash. Not sure how or where that could happen.

summary: - gnome-shell crashed with SIGSEGV in __GI_getenv()
+ gnome-shell crashed with SIGSEGV in __GI_getenv() from [g_getenv() from]
+ should_drop_message()
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: gnome-shell crashed with SIGSEGV in __GI_getenv() from [g_getenv() from] should_drop_message()

The "how" might be a mistaken use of putenv() in which the caller has forgotten that the parameter string needs to live forever.

summary: - gnome-shell crashed with SIGSEGV in __GI_getenv() from [g_getenv() from]
- should_drop_message()
+ gnome-shell crashed with SIGSEGV in __GI_getenv("MESSAGES_DEBUG") from
+ [g_getenv() from] should_drop_message()
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This is probably fixed by the fix for bug 2036651.

information type: Private → Public
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.