gnome-shell crashed with SIGSEGV in meta_monitor_manager_kms_apply_crtc_mode()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I'm not sure when this happened, I think it was switching from tty3 back to my session.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.26.2-0ubuntu2
ProcVersionSign
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu9
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Tue Feb 13 14:12:33 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/
GsettingsChanges:
InstallationDate: Installed on 2017-10-23 (112 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/false
SegvAnalysis:
Segfault happened at: 0x7f29b362b35f <meta_monitor_
PC (0x7f29b362b35f) ok
source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
meta_monitor_
meta_renderer_
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
Title: gnome-shell crashed with SIGSEGV in meta_monitor_
UpgradeStatus: Upgraded to bionic on 2018-01-23 (21 days ago)
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 #1725160, 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.