gnome-shell crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
An error message popped up when logged in into my account.
lsb_release -rd
Description: Ubuntu Artful Aardvark (development branch)
Release: 17.10
apt-cache policy gnome-shell
gnome-shell:
Installed: 3.25.91-0ubuntu3
Candidate: 3.25.91-0ubuntu3
Version table:
*** 3.25.91-0ubuntu3 500
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.25.91-0ubuntu3
ProcVersionSign
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Sep 9 18:39:45 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/
GsettingsChanges:
InstallationDate: Installed on 2017-07-26 (46 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_CA.UTF-8
SHELL=/bin/false
SegvAnalysis:
Segfault happened at: 0x7fa7a18dd836: mov 0x1a0(%rax),%rax
PC (0x7fa7a18dd836) 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/
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
drmHandleEvent () from /usr/lib/
meta_monitor_
Title: gnome-shell crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
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.