Ubuntu
gnome-shell package

gnome-shell crashed with SIGSEGV at ?+a7c

Bug #1964254 reported by Norbert Cserpnyák on 2022-03-08

This bug report is a duplicate of: Bug #1964120: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack]). Edit Remove

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gnome-shell (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 8 18:28:18 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2022-03-08 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220305)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: mutter-common 41.3-3ubuntu1
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
#0 0x00007fc4fe18aa7c in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7ffd499cdaa0
StacktraceTop: ?? ()
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

See original description

Tags:

Revision history for this message

Norbert Cserpnyák (norbex2003) wrote on 2022-03-08:

#1

Dependencies.txt Edit (22.4 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (611 bytes, text/plain; charset="utf-8")
GsettingsChanges.txt Edit (858 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (118.8 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (185.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Registers.txt Edit (994 bytes, text/plain; charset="utf-8")
SegvAnalysis.txt Edit (187 bytes, text/plain; charset="utf-8")
ShellJournal.txt Edit (27.5 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.9 KiB, text/plain; charset="utf-8")
monitors.xml.txt Edit (762 bytes, text/plain; charset="utf-8")

description:	updated
information type:	Private → Public

Revision history for this message

Apport retracing service (apport) wrote on 2022-03-08:

#2

Stacktrace:
#0 0x00007fc4fe18aa7c in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7ffd499cdaa0
StacktraceSource: #0 0x00007fc4fe18aa7c in ?? ()
StacktraceTop: ?? ()

tags:

removed: need-amd64-retrace

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2022-03-09:

#3

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1964120, so it 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. Feel free to continue to report any other bugs you may find.

summary:

- gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV at ?+a7c

Revision history for this message

Apport retracing service (apport) wrote on 2022-03-09:

#4

Stacktrace:
#0 0x00007fc4fe18aa7c in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7ffd499cdaa0
StacktraceSource: #0 0x00007fc4fe18aa7c in ?? ()
StacktraceTop: ?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2022-03-09: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (1.9 KiB, text/plain)

Changed in gnome-shell (Ubuntu):
status:	New → Invalid

Revision history for this message

Apport retracing service (apport) wrote on 2022-03-09: Crash report cannot be processed

#6

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for libcrypt1
no debug symbol package found for libjpeg-turbo8
no debug symbol package found for libgdk-pixbuf-2.0-0

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #1964120 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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