budgie-wm crashed with SIGSEGV in __GI___pthread_mutex_lock() with mutter 3.23.91

Bug #1669584 reported by Sander Jonkers
56
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Mutter
Unknown
Critical
budgie-desktop (Ubuntu)
Fix Released
Critical
Unassigned
mutter (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

With zesty's current mutter 3.23.91-0ubuntu1, Budgie crashes after trying to launch some apps.

Downgrading mutter to 3.23.90-0ubuntu2 fixes this.

--

After a cold reboot + restart, I got this crash, and had to re-login, and then the same happened.

I then logged in on my plain Ubuntu desktop.

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: budgie-core 10.2.9-3ubuntu3
Uname: Linux 4.10.0-041000-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Thu Mar 2 21:48:42 2017
ExecutablePath: /usr/bin/budgie-wm
InstallationDate: Installed on 2017-02-19 (11 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170219)
ProcCmdline: budgie-wm
Signal: 11
SourcePackage: budgie-desktop
StacktraceTop:
 __GI___pthread_mutex_lock (mutex=0x6c75646f6d5f6b74) at ../nptl/pthread_mutex_lock.c:67
 XrmQGetResource () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XGetDefault () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
Title: budgie-wm crashed with SIGSEGV in __GI___pthread_mutex_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

StacktraceTop:
 __GI___pthread_mutex_lock (mutex=0x6c75646f6d5f6b74) at ../nptl/pthread_mutex_lock.c:67
 XrmQGetResource (db=0x5608f21aff90, names=names@entry=0x7ffccb88ba40, classes=classes@entry=0x7ffccb88ba50, pType=pType@entry=0x7ffccb88ba2c, pValue=pValue@entry=0x7ffccb88ba30) at ../../src/Xrm.c:2549
 XGetDefault (dpy=dpy@entry=0x5608f20df9a0, prog=prog@entry=0x7fcb9a93e081 "Xft", name=name@entry=0x7fcb9a93f854 "antialias") at ../../src/GetDflt.c:231
 get_boolean_default (value=<synthetic pointer>, option=0x7fcb9a93f854 "antialias", dpy=0x5608f20df9a0) at ../../../../src/cairo-xlib-screen.c:98
 _cairo_xlib_init_screen_font_options (info=0x5608f24e99b0, dpy=0x5608f20df9a0) at ../../../../src/cairo-xlib-screen.c:146

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 budgie-desktop (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Jeremy Bícha (jbicha)
information type: Private → Public
description: updated
summary: - budgie-wm crashed with SIGSEGV in __GI___pthread_mutex_lock()
+ budgie-wm crashed with SIGSEGV in __GI___pthread_mutex_lock() with
+ mutter 3.23.91
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in budgie-desktop (Ubuntu):
status: New → Confirmed
Jeremy Bícha (jbicha)
Changed in budgie-desktop (Ubuntu):
importance: Medium → Critical
Revision history for this message
fossfreedom (fossfreedom) wrote :

Ran a git bisect on mutter:

https://github.com/GNOME/mutter/commit/383ba566bd7c2a76d0856015a66e47caedef06b6

confirmed - final git bisect bad displays the above commit

I built a local mutter v2.23.91 package with a reverse patch of that commit. All is well. I really don't understand though the code behind that commit nor the logic in the linked bugzilla report though :(

Revision history for this message
fossfreedom (fossfreedom) wrote :

created a gnome bugzilla report: https://bugzilla.gnome.org/show_bug.cgi?id=779538

Jeremy Bícha (jbicha)
Changed in mutter (Ubuntu):
importance: Undecided → Critical
status: New → Fix Committed
Changed in mutter:
importance: Unknown → Critical
status: Unknown → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mutter - 3.23.91-0ubuntu1.1

---------------
mutter (3.23.91-0ubuntu1.1) zesty; urgency=medium

  * Add git_revert_call_threaded_swap.patch:
    - Revert patch that caused Budgie to crash (LP: #1669584)

 -- Jeremy Bicha <email address hidden> Thu, 02 Mar 2017 16:09:36 -0500

Changed in mutter (Ubuntu):
status: Fix Committed → Fix Released
Changed in mutter:
status: Confirmed → Unknown
Changed in budgie-desktop (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.