gnome-shell crashed with SIGSEGV in g_closure_invoke()

Bug #1714784 reported by shemgp
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
New
Undecided
Unassigned

Bug Description

Upgraded Artful to gnome-shell 3.25.91-0ubuntu2 and did a restart and this crash popped up.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.25.91-0ubuntu2
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sun Sep 3 22:33:43 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2017-07-17 (48 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170716)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_PH:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_PH.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7f34b0c56836: mov 0x1a0(%rax),%rax
 PC (0x7f34b0c56836) ok
 source "0x1a0(%rax)" (0x000001a0) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 drmHandleEvent () from /usr/lib/x86_64-linux-gnu/libdrm.so.2
 meta_monitor_manager_kms_wait_for_flip () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
Title: gnome-shell crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
shemgp (shemgp) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1714330, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
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.