gnome-shell crashed with SIGSEGV in __GI_getenv("EXPAT_ENTITY_DEBUG") from getDebugLevel() from parserInit()

Bug #2034524 reported by James Page
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

gnome-shell crashes when session is locked - either manually or as a result of a timeout event as configured under security/power management settings.

Session is lost I have to log back in once this happens.

ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45~beta.1-0ubuntu2
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Wed Sep 6 08:34:06 2023
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1693259374
GsettingsChanges:

InstallationDate: Installed on 2022-09-26 (345 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /var/lib/gdm3
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 SHELL=/bin/false
 XDG_RUNTIME_DIR=<set>
RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 __GI_getenv (name=0x7f8a241b7def "EXPAT_ENTITY_DEBUG") at ./stdlib/getenv.c:31
 ??? () at /lib/x86_64-linux-gnu/libexpat.so.1
 ??? () at /lib/x86_64-linux-gnu/libexpat.so.1
 ??? () at /lib/x86_64-linux-gnu/libexpat.so.1
 ??? () at /lib/x86_64-linux-gnu/libfontconfig.so.1
UpgradeStatus: Upgraded to mantic on 2023-06-16 (82 days ago)
UserGroups: N/A
separator:

Revision history for this message
James Page (james-page) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __GI_getenv (name=name@entry=0x7f8a241b7def "EXPAT_ENTITY_DEBUG") at ./stdlib/getenv.c:31
 getDebugLevel.constprop.0 (variableName=variableName@entry=0x7f8a241b7def "EXPAT_ENTITY_DEBUG", defaultDebugLevel=0) at ../../src/lib/xmlparse.c:8389
 parserInit (parser=parser@entry=0x7f89bc0131e0, encodingName=encodingName@entry=0x7f8a26f9397a "UTF-8") at ../../src/lib/xmlparse.c:1175
 parserCreate (encodingName=encodingName@entry=0x7f8a26f9397a "UTF-8", memsuite=memsuite@entry=0x0, nameSep=nameSep@entry=0x0, dtd=dtd@entry=0x0) at ../../src/lib/xmlparse.c:1069
 XML_ParserCreate_MM (encodingName=encodingName@entry=0x7f8a26f9397a "UTF-8", memsuite=memsuite@entry=0x0, nameSep=nameSep@entry=0x0) at ../../src/lib/xmlparse.c:969

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 : Re: gnome-shell crashed with SIGSEGV in __GI_getenv()

Looks like the environment block has been corrupted (otherwise getenv wouldn't crash). This can happen if some code called putenv() but then freed the memory instead of leaking it as it should.

See also bug 1979118 and bug 2027830.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I can't find any code in mutter, gnome-shell or our extensions making that mistake. Maybe in a library?

summary: - gnome-shell crashed with SIGSEGV in __GI_getenv()
+ gnome-shell crashed with SIGSEGV in __GI_getenv() from getDebugLevel()
+ from parserInit()
summary: - gnome-shell crashed with SIGSEGV in __GI_getenv() from getDebugLevel()
- from parserInit()
+ gnome-shell crashed with SIGSEGV in __GI_getenv("EXPAT_ENTITY_DEBUG")
+ from getDebugLevel() from parserInit()
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

See also bug 2039340.

information type: Private → Public
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This is probably fixed by the fix for bug 2036651.

tags: added: noble
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I just hit this crash after logging out of Noble. gdm's gnome-shell instance to restart the login screen crashed on first attempt. It worked on the second attempt using Xorg instead of Wayland.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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