gnome-shell crashed with SIGSEGV in meta_monitor_manager_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()

Bug #1725160 reported by Léon Hagenaars-Keus on 2017-10-20
76
This bug affects 11 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Medium
Unassigned

Bug Description

https://errors.ubuntu.com/problem/ae8fffc26dce834957d02421350f3841472b2ad7

---

Having an NVidia Optimus type laptop graphics card, this happened after installing nvidia drivers (from the software update/additional drivers screen) and rebooting in discrete mode (so NVidia only)

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Fri Oct 20 08:49:10 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2017-04-29 (173 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=nl_NL.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7fdd1a378a6f <meta_monitor_manager_kms_apply_crtc_mode+207>: mov 0x8(%rax),%rcx
 PC (0x7fdd1a378a6f) 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_manager_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 meta_renderer_native_finish_frame () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so
 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so
Title: gnome-shell crashed with SIGSEGV in meta_monitor_manager_kms_apply_crtc_mode()
UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
UserGroups:

StacktraceTop:
 meta_monitor_manager_kms_apply_crtc_mode (manager_kms=manager_kms@entry=0x562760a4f1b0, crtc=0x562760d24a40, x=x@entry=0, y=y@entry=0, fb_id=fb_id@entry=0) at backends/native/meta-monitor-manager-kms.c:1649
 meta_renderer_native_finish_frame (renderer_native=0x562760a48550) at backends/native/meta-renderer-native.c:1801
 clutter_stage_cogl_redraw (stage_window=0x562760d04390) at cogl/clutter-stage-cogl.c:871
 meta_stage_native_redraw (stage_window=0x562760d04390) at backends/native/meta-stage-native.c:301
 clutter_stage_do_redraw (stage=0x562760a5de70) at clutter-stage.c:1121

Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Daniel van Vugt (vanvugt) wrote :

Many/most laptops with hybrid graphics don't have the discrete GPU wired to the internal screen. If that includes you then discrete-only mode might only work with an external monitor attached. Because typically the Nvidia GPU is wired to at least one HDMI/DisplayPort, but not usually the laptop panel. Usually only the Intel GPU is attached to the laptop LCD.

information type: Private → Public
summary: gnome-shell crashed with SIGSEGV in
- meta_monitor_manager_kms_apply_crtc_mode()
+ meta_monitor_manager_kms_apply_crtc_mode() from
+ meta_renderer_native_finish_frame()
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed

My laptop (a Clevo) has the intel hooked up to the internal pannel. All other 3 connections (one hdmi en two mini-displayports) are only hooked up to the nvidia card.
Intel can't see the 3 external connections. Nvidia 'passes through' the intel card.
This worked like a charm when running in 'discrete' mode in ubuntu 17.04.

tags: added: bionic
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers