gnome-shell crashed with SIGSEGV in meta_window_is_on_primary_monitor()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
gnome-shell segfaults every time I turn off the monitor connected via HDMI (whether running in Wayland or X11). The HDMI monitor is the only one connected to the system, so it has to be configured as the primary.
The crash doesn't happen with my last snapshot from Aug 11th, so it's a regression since then.
I'm guessing this is different from bug #1714886 because that one occurs immediately after login, rather than when the monitor is turned off.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.0-0ubuntu1
ProcVersionSign
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 27 16:29:18 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-02-27 (211 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170225)
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=en_AU:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_AU.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f143055e434 <meta_window_
PC (0x7f143055e434) ok
source "0x2c(%rax)" (0x0000002c) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
meta_window_
() at /usr/lib/
meta_window_
meta_window_
g_slist_foreach () at /lib/x86_
Title: gnome-shell crashed with SIGSEGV in meta_window_
UpgradeStatus: Upgraded to artful on 2017-06-26 (92 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
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 #1714886, 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.