gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Just got the crash pop-up; no idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.2-
ProcVersionSign
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Jul 14 16:18:23 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/
GsettingsChanges:
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: 0x7f61c0a50dd7 <meta_gpu_
PC (0x7f61c0a50dd7) ok
source "0x20(%rax)" (0x00000020) not located in a known VMA region (needed readable region)!
destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
meta_gpu_
meta_renderer_
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: gnome-shell crashed with SIGSEGV in meta_gpu_
UpgradeStatus: Upgraded to bionic on 2018-05-19 (56 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 #1754949, 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.