gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Seems similar to some other reported crashes but with a different function call error. When turning back on a monitor the gnome-shell crashes. The crash does not occur until I attempt to turn the monitor on as it is happily playing sound and media buttons work with the screen off.
Intel NUC with i7-5557U CPU and Iris 6100 graphics, happy to provide other information if helpful.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu5
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 11 10:36:27 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/
ExecutableTimes
GsettingsChanges:
b'org.gnome.shell' b'favorite-apps' b"['org.
b'org.
b'org.
b'org.
b'org.
InstallationDate: Installed on 2017-05-28 (167 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/
ProcCwd: /home/neltnerb
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7eff424cde04 <meta_window_
PC (0x7eff424cde04) 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 () from /usr/lib/
ffi_call () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: gnome-shell crashed with SIGSEGV in meta_window_
UpgradeStatus: Upgraded to artful on 2017-10-21 (20 days ago)
UserGroups: adm cdrom dialout 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.