gnome-shell crashed with SIGSEGV in __GI_getenv("NTCONFIG_SYSROOT") from IA__FcConfigGetSysRoot()

Bug #1979118 reported by corrado venturini
64
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Ubuntu
Fix Released
Medium
Unassigned

Bug Description

https://errors.ubuntu.com/problem/dea417d91da22f2d4de0980b3be8d98be8f8c100

---

Just started, only firefox-trunk active

ProblemType: Crash
DistroRelease: Ubuntu 22.10
Package: gnome-shell 42.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.21.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Jun 18 15:41:24 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2022-05-14 (34 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220512)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 42.2-1ubuntu1
SegvAnalysis:
 Segfault happened at: 0x7f6ea4325c1d <__GI_getenv+173>: cmp (%r12),%bp
 PC (0x7f6ea4325c1d) ok
 source "(%r12)" (0xfca16778d75cc123) not located in a known VMA region (needed readable region)!
 destination "%bp" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 __GI_getenv (name=0x7f6ea355531e "NTCONFIG_SYSROOT") at ./stdlib/getenv.c:84
 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
 FcConfigBuildFonts () from /lib/x86_64-linux-gnu/libfontconfig.so.1
 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
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
corrado venturini (corradoventu) wrote :
information type: Private → Public
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: gnome-shell crashed with SIGSEGV in __GI_getenv("NTCONFIG_SYSROOT")
summary: - gnome-shell crashed with SIGSEGV in __GI_getenv()
+ gnome-shell crashed with SIGSEGV in __GI_getenv("NTCONFIG_SYSROOT")
Changed in gnome-shell (Ubuntu):
status: New → Confirmed
tags: added: jammy
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Crashing in getenv with a valid parameter like this should not be possible so I think some heap corruption must have occurred before the crash.

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

StacktraceTop:
 __GI_getenv (name=0x7f6ea355531e "NTCONFIG_SYSROOT", name@entry=0x7f6ea355531c "FONTCONFIG_SYSROOT") at ./stdlib/getenv.c:84
 IA__FcConfigGetSysRoot (config=<optimized out>) at /build/fontconfig-Aho6Ty/fontconfig-2.13.1/src/fccfg.c:2467
 IA__FcConfigGetSysRoot (config=<optimized out>) at /build/fontconfig-Aho6Ty/fontconfig-2.13.1/src/fccfg.c:2455
 FcDirCacheReadUUID (dir=dir@entry=0x7f6e68003390 "/usr/share/fonts/truetype/lohit-oriya", config=config@entry=0x7f6e68000b70) at /build/fontconfig-Aho6Ty/fontconfig-2.13.1/src/fccache.c:186
 IA__FcDirCacheLoad (cache_file=0x0, config=0x7f6e68000b70, dir=0x7f6e68003390 "/usr/share/fonts/truetype/lohit-oriya") at /build/fontconfig-Aho6Ty/fontconfig-2.13.1/src/fccache.c:1054

tags: removed: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
summary: - gnome-shell crashed with SIGSEGV in __GI_getenv("NTCONFIG_SYSROOT")
+ gnome-shell crashed with SIGSEGV in __GI_getenv("NTCONFIG_SYSROOT") from
+ IA__FcConfigGetSysRoot()
Revision history for this message
Mario Limonciello (superm1) wrote :

> Crashing in getenv with a valid parameter like this should not be possible so I think some heap corruption must have occurred before the crash.

So at least as a hint coming from a report that was marked as a duplicate of this - at least for me it's specifically when the system had a monitor connected and it was disconnected that this issue occurs.

Revision history for this message
corrado venturini (corradoventu) wrote :

No longer occurred due to fix or new version. Marked as Invalid.

Changed in gnome-shell (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Changed in gnome-shell (Ubuntu):
status: Invalid → Fix Released
affects: gnome-shell (Ubuntu) → ubuntu
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.