gnome-shell crashed with SIGSEGV at ...90ffb

Bug #2012974 reported by Derwin McGeary
174
This bug affects 18 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Running preview of 23.04, I click Firefox, the screen is black, and it hangs around. Eventually it pops up the bug report dialog, and then, oddly, launches Firefox to let me tell you about it!

ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.0-2ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
Uname: Linux 6.2.0-18-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 27 20:18:21 2023
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2023-03-27 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230324)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
RelatedPackageVersions: mutter-common 44.0-1ubuntu1
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
 #0 0x00007f747b290ffb in ?? ()
 No symbol table info available.
 Backtrace stopped: Cannot access memory at address 0x7ffe3242f220
StacktraceTop: ?? ()
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
separator:

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

Stacktrace:
 #0 0x00007f747b290ffb in ?? ()
 No symbol table info available.
 Backtrace stopped: Cannot access memory at address 0x7ffe3242f220
StacktraceSource: #0 0x00007f747b290ffb 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
Daniel van Vugt (vanvugt) wrote :

Seems like this is the new form of bug 2012075.

summary: - gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV at ...90ffb
summary: - gnome-shell crashed with SIGSEGV at ...90ffb
+ gnome-shell 44.0-2ubuntu1 crashed with SIGSEGV at ...90ffb
summary: - gnome-shell 44.0-2ubuntu1 crashed with SIGSEGV at ...90ffb
+ gnome-shell crashed with SIGSEGV at ...90ffb
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Since most gnome-shell crashes in Ubuntu 23.04 are bug 1966905 right now, I would hazard a guess that will fix it when the fix is released (and verified as working).

Revision history for this message
Derwin McGeary (djm62) wrote :

Thank you for taking the time to look into it!

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

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

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
information type: Private → Public
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Most crashes in 23.04 are now bug 1974293, which occurs on logout but you won't be told about it till you log in again.

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

Still happening (bug 2012974) even with the fix for bug 1974293.

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

I think the limiting factor is bug 2015857 at the moment.

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.