gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
No sure what other details i can provide
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.0-0ubuntu1
ProcVersionSign
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 29 20:04:04 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2016-11-04 (510 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f59a3875c24 <meta_window_
PC (0x7f59a3875c24) 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 2018-03-28 (2 days ago)
UserGroups: adm cdrom dip docker 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.