Ubuntu Jammy gnome-shell crashed with SIGSEGV

Bug #1964463 reported by Leó Kolbeinsson
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Testing Ubuntu Jammy Live session daily iso 10-03-2022

gnome-shell crashed after selecting Firefox snap

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.467
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 10 10:13:28 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'41.3'"
 b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.notifications' b'application-children' b"['apport-gtk']"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310)
ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
ProcEnviron:
 PATH=(custom, no user)
 LANG=C.UTF-8
 XDG_RUNTIME_DIR=<set>
RelatedPackageVersions: mutter-common 41.3-3ubuntu1
SegvAnalysis:
 Segfault happened at: 0x7f04cd0f7f44: mov (%rsi),%rax
 PC (0x7f04cd0f7f44) ok
 source "(%rsi)" (0x2d78d4200000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
 #0 0x00007f04cd0f7f44 in ?? ()
 No symbol table info available.
 Backtrace stopped: Cannot access memory at address 0x7fff167a9950
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:

Revision history for this message
Leó Kolbeinsson (leok) wrote :
information type: Private → Public
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
description: updated
Revision history for this message
Apport retracing service (apport) wrote :

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

tags: removed: need-amd64-retrace
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

It looks like the crash address has shifted slightly in the latest mozjs version but this is almost certainly bug 1964458.

Still waiting for the bots to try and retrace it.

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

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

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-shell (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

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!

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.