gnome-shell crashed with SIGSEGV in g_main_context_dispatch()

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

Bug Description

Unexpected Gnome-shell restart.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.24.3-0ubuntu2
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Thu Aug 17 10:44:07 2017
DisplayManager: gdm3
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-shell
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f4914f66615: testb $0x1,(%rax)
 PC (0x7f4914f66615) ok
 source "$0x1" ok
 destination "(%rax)" (0x7f48a54fffe8) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/libgjs.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 meta_run () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0
Title: gnome-shell crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to artful on 2017-08-14 (2 days ago)
UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin plugdev sambashare sudo ubridge

Revision history for this message
omid.1985 (omid-1985) 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 #1689863, 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.