gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.26.2-0ubuntu2
Uname: Linux 4.15.0-
ApportVersion: 2.20.8-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 22 21:04:51 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-11-08 (45 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_CA.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fb9635672d4 <meta_window_
PC (0x7fb9635672d4) ok
source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
meta_window_
ffi_call_unix64 () at /usr/lib/
ffi_call () at /usr/lib/
() at /usr/lib/
() at /usr/lib/
Title: gnome-shell crashed with SIGSEGV in meta_window_
UpgradeStatus: Upgraded to bionic on 2017-11-20 (32 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #1724439, 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.