gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from meta_monitor_get_vendor() from logical_monitor_has_monitor()

Bug #1724102 reported by markackerman8@gmail.com
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

17.10 Beta Fully Updated and re-installed in a fresh partition for best results.

When screen went blank at time out, returning it from "its' hibernation state" screws up "workspace to Dock"

So Alt+F2 and "r" brought it back but other things like terminal stopped working.

Trying to help, Mark

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Mon Oct 16 16:12:44 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2017-10-16 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7fbbde5c8543 <meta_monitor_get_main_output+3>: jmpq *0x88(%rax)
 PC (0x7fbbde5c8543) ok
 source "*0x88(%rax)" ok
 SP (0x7fff9bbdef08) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 meta_monitor_get_main_output () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 meta_monitor_get_vendor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
markackerman8@gmail.com (markackerman8) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 meta_monitor_get_main_output (monitor=0x55e46412a680) at backends/meta-monitor.c:191
 meta_monitor_get_vendor (monitor=monitor@entry=0x55e46412a680) at backends/meta-monitor.c:317
 logical_monitor_has_monitor (monitor_manager=<optimized out>, serial=<optimized out>, product=0x55e463571ee0 "0x046f", vendor=0x55e4647dd150 "LGD", logical_monitor=0x55e463eb3190) at backends/meta-input-settings.c:788
 meta_input_settings_find_logical_monitor (input_settings=input_settings@entry=0x55e461fbe430, settings=settings@entry=0x55e464660f00, device=device@entry=0x55e4623625f0) at backends/meta-input-settings.c:832
 update_device_display (input_settings=input_settings@entry=0x55e461fbe430, settings=0x55e464660f00, device=0x55e4623625f0) at backends/meta-input-settings.c:917

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
summary: - gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
+ gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from
+ meta_monitor_get_vendor() from logical_monitor_has_monitor()
information type: Private → Public
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Similar to bug 1703668

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.