gnome-shell crashed with SIGSEGV in g_main_context_dispatch()
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
ProcVersionSign
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/
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=en_AU:en
PATH=(custom, no user)
XDG_RUNTIME_
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/
g_main_
?? () from /lib/x86_
g_main_loop_run () from /lib/x86_
meta_run () from /usr/lib/
Title: gnome-shell crashed with SIGSEGV in g_main_
UpgradeStatus: Upgraded to artful on 2017-08-14 (2 days ago)
UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin plugdev sambashare sudo ubridge
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.