gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Submitting crash as instructed in bug 1769720.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSign
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Tue May 8 14:34:19 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-05-19 (354 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f399f4fa210 <meta_monitor_
PC (0x7f399f4fa210) ok
source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
meta_monitor_
meta_monitor_
meta_monitor_
meta_monitor_
meta_monitor_
Title: gnome-shell crashed with SIGSEGV in meta_monitor_
UpgradeStatus: Upgraded to bionic on 2018-04-27 (11 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo vboxusers wireshark
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 #1723615, 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.