gnome-shell crashed with SIGSEGV in meta_drm_buffer_gbm_finalize()

Bug #2036336 reported by Amartya Datta Gupta
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mutter
New
Unknown
gnome-shell (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

The gnome shell always starts a new session when trying to wake up from sleep. On waking up, after I enter the password, the screen turns black and the login screen appears.

ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45~rc-0ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 16 22:00:54 2023
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2023-09-01 (16 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
RelatedPackageVersions: mutter-common 45~rc-0ubuntu2
SegvAnalysis:
 Segfault happened at: 0x7f06f00000f8: add (%rax),%al
 PC (0x7f06f00000f8) in non-executable VMA region: 0x7f06f0000000-0x7f06f0001000 r--p /usr/lib/x86_64-linux-gnu/girepository-1.0/DBus-1.0.typelib
 source "(%rax)" (0x7f06f00000f8) ok
 destination "%al" ok
SegvReason: executing non-writable VMA /usr/lib/x86_64-linux-gnu/girepository-1.0/DBus-1.0.typelib
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0
 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0
 g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in g_object_unref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
separator:

Revision history for this message
Amartya Datta Gupta (amartya00) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 meta_drm_buffer_gbm_finalize (object=0x5582083cfbd0) at ../src/backends/native/meta-drm-buffer-gbm.c:374
 g_object_unref (_object=0x5582083cfbd0) at ../../../gobject/gobject.c:3941
 g_object_unref (_object=0x5582083cfbd0) at ../../../gobject/gobject.c:3805
 g_set_object (new_object=0x5582078f1320, object_ptr=0x7f06ec054f10) at /usr/include/glib-2.0/gobject/gobject.h:769

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.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 g_object_unref()
+ gnome-shell crashed with SIGSEGV in meta_drm_buffer_gbm_finalize()
tags: removed: need-amd64-retrace
tags: added: triple-buffering
Changed in gnome-shell (Ubuntu):
assignee: nobody → Daniel van Vugt (vanvugt)
tags: added: hybrid i915 multigpu nvidia
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Sounds like bug 1969422, but that was meant to be fixed last year:

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1548259

Changed in gnome-shell (Ubuntu):
status: New → In Progress
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I've been trying for hours and can't find a way to reproduce this bug.

Please update your system to 45.0:

  sudo apt update
  sudo apt full-upgrade

and then reboot.

If the crash happens again after that then please provide more details about the circumstances, such as:

  * If it only happens when the secondary monitor is connected
  * If it only happens when a window is fullscreen/maximized

Please also confirm your libmutter-13-0 package is version 45.0-1ubuntu1.

Separately to all that I'm waiting for errors.ubuntu.com to start working again so we can see more details about this crash from other machines.

Changed in gnome-shell (Ubuntu):
status: In Progress → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

There haven't been any reports of this since 23.10 was released so I'm going to start the clock to let it expire in 2 months...

Changed in gnome-shell (Ubuntu):
assignee: Daniel van Vugt (vanvugt) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-shell (Ubuntu):
status: Incomplete → Expired
Changed in mutter:
status: Unknown → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Maybe this will get reopened since a very similar issue is now reported upstream: https://gitlab.gnome.org/GNOME/mutter/-/issues/3277

information type: Private → Public
Changed in gnome-shell (Ubuntu):
status: Expired → Confirmed
tags: added: udeng-1398
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.