gnome-shell crashed with SIGSEGV

Bug #1967176 reported by Vladimir
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

1) lsb_release -rd
Description: Ubuntu Jammy Jellyfish (development branch)
Release: 22.04

2) apt-cache policy gnome-shell
gnome-shell:
  Installed: 42~beta-1ubuntu3
  Candidate: 42~beta-1ubuntu3
  Version table:
 *** 42~beta-1ubuntu3 500
        500 http://mirror.docker.ru/ubuntu jammy/main amd64 Packages
        100 /var/lib/dpkg/status

nvidia 1030. nvidia-driver-510

3) What you expected to happen
just logout and login again

4) What happened instead
after logout and login again, apport reported this crash.

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 22:40:45 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2022-03-25 (4 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANG=ru_RU.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
 #0 0x00007ffbc79eda7c in ?? ()
 No symbol table info available.
 Backtrace stopped: Cannot access memory at address 0x7ffc1a2ffa60
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
Vladimir (javafors) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

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

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

Thank you for taking the time to report this bug and helping to make Ubuntu better.

However, processing it in order to get sufficient information for the developers failed (it does not generate an useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report. 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!

Changed in gnome-shell (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote :

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

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
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 libjpeg-turbo8
no debug symbol package found for libcrypt1
no debug symbol package found for libnvidia-gl-510

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!

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

I forgot we also have bug 1964120 for this.

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.