gnome-shell crashed with SIGABRT: libmutter:ERROR:../src/backends/x11/meta-barrier-x11.c:231:meta_x11_barriers_free: assertion failed: (g_hash_table_size (x11_barriers->barriers) == 0)

Bug #2036889 reported by Claus7
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Mutter
Fix Released
Unknown
gnome-shell (Ubuntu)
Fix Released
Medium
Daniel van Vugt
mutter (Ubuntu)
Invalid
Medium
Daniel van Vugt

Bug Description

it just showed this report

ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.0-1ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 21 13:19:48 2023
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2023-09-02 (19 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 45.0-1ubuntu1
Signal: 6
SourcePackage: gnome-shell
Stacktrace:
 #0 0x00007fcc84c9999b in ?? ()
 No symbol table info available.
 Backtrace stopped: Cannot access memory at address 0x7ffe88bb8120
StacktraceTop: ?? ()
Title: gnome-shell crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
separator:

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

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

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
summary: - gnome-shell crashed with SIGABRT
+ gnome-shell crashed with SIGABRT:
+ libmutter:ERROR:../src/backends/x11/meta-
+ barrier-x11.c:231:meta_x11_barriers_free: assertion failed:
+ (g_hash_table_size (x11_barriers->barriers) == 0)
affects: gnome-shell (Ubuntu) → mutter (Ubuntu)
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 mutter (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

As far as I know this only happens on logout so setting Importance to Low.

Changed in mutter (Ubuntu):
importance: Undecided → Low
Changed in mutter:
status: Unknown → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Bumped importance because recurring error popups will be annoying in production, and I think bug 2036440 in the live session is the same bug.

Changed in mutter (Ubuntu):
importance: Low → Medium
assignee: nobody → Daniel van Vugt (vanvugt)
status: Confirmed → Triaged
milestone: none → ubuntu-23.10
Changed in mutter (Ubuntu):
status: Triaged → In Progress
Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
assignee: nobody → Daniel van Vugt (vanvugt)
milestone: none → ubuntu-23.10
status: New → In Progress
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Changed in mutter (Ubuntu):
status: In Progress → Invalid
milestone: ubuntu-23.10 → none
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-shell - 45.0-1ubuntu2

---------------
gnome-shell (45.0-1ubuntu2) mantic; urgency=medium

  * Cherry-pick 2 commits from future 45.1:
    - Fix crash at shutdown (LP: #2036889)
    - Fix indefinite inhibition of direct scanout when closing the Overview

 -- Jeremy Bícha <email address hidden> Tue, 03 Oct 2023 14:16:54 -0400

Changed in gnome-shell (Ubuntu):
status: In Progress → Fix Released
Changed in mutter:
status: New → Fix Released
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.