gnome-shell crashed with SIGSEGV in meta_window_is_on_primary_monitor()

[Koos]

https://errors.ubuntu.com/problem/2248f9a7d43e5e9a3bba2ac8364590ed8b7361a7

---

This crash appears after login in, when gnome-shell restarts it seems to be stable.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.25.91-0ubuntu2
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 4 09:18:43 2017
DisplayManager: gdm3
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2017-04-03 (153 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7ff4e23f8b24 <meta_window_is_on_primary_monitor+4>: mov 0x2c(%rax),%eax
 PC (0x7ff4e23f8b24) 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_is_on_primary_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 meta_window_on_all_workspaces_changed () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 meta_window_update_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in meta_window_is_on_primary_monitor()
UpgradeStatus: Upgraded to artful on 2017-08-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 meta_window_is_on_primary_monitor (window=window@entry=0xee34d09130) at core/window.c:2865
 should_be_on_all_workspaces (window=0xee34d09130) at core/window.c:4481
 meta_window_on_all_workspaces_changed (window=window@entry=0xee34d09130) at core/window.c:4487
 meta_window_update_monitor (window=0xee34d09130, user_op=0) at core/window.c:3619
 g_slist_foreach (list=<optimized out>, list@entry=0xee32f60570, func=func@entry=0x7ff4e23ff400 <meta_window_update_for_monitors_changed>, user_data=user_data@entry=0x0) at ../../../../glib/gslist.c:880

[Launchpad Janitor (janitor)]

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

[Rocko (rockorequin)]

FWIW, I can reproduce this crash every time simply by turning off the HDMI monitor attached to my NUC (ref bug #1719808), and it's a regression since early August (my Aug 11 snapshot doesn't have this problem).

[Jh (jh+jh)]

Well i didnt think of that, so I tried it, too. When I turn off my Display that is connected via Displayport, the Gnomeshell is killed after turning the Screen on again. After turning on the Screen the login-window can be seen.
When you log in, its a new Session.
That would explain why in Bug #1718671 the session is only crashing after when you want to unlock the Screen, because the Display was turned off after locking the screen.

[Daniel van Vugt (vanvugt)]

Looks like:
https://bugzilla.gnome.org/show_bug.cgi?id=730551

[Daniel van Vugt (vanvugt)]

And also:
https://bugzilla.gnome.org/show_bug.cgi?id=787637

maybe related: bug 1717170

[Daniel van Vugt (vanvugt)]

And see also https://errors.ubuntu.com/problem/2248f9a7d43e5e9a3bba2ac8364590ed8b7361a7

[Andrew Hatfield (autarkis13)]

This bug seems to have the same symptoms as
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1722353
i.e. the session crashes when an HDMI or DP connected monitor is turned back on.

Andrew

[Daniel van Vugt (vanvugt)]

No, bug 1722353 is already fixed :)

[Rocko (rockorequin)]

So is there any progress on this? I can't use gnome-shell because of it, even with Ubuntu 18.04.

[Daniel van Vugt (vanvugt)]

I'm really not sure we're linking to the right upstream bugs still, or that we've captured all the right error reports from errors.ubuntu.com.

Possibly this is related and is in progress:
https://bugzilla.gnome.org/show_bug.cgi?id=788882

As for Ubuntu crash reports, the only link we have suggests this particular crash in meta_window_is_on_primary_monitor universally stopped happening after artful gnome-shell version 3.26.0-0ubuntu2, and never happened in bionic:

https://errors.ubuntu.com/problem/2248f9a7d43e5e9a3bba2ac8364590ed8b7361a7

So _if_ this is the right bug for us to be commenting on then we probably need to find a different but similar error report. Otherwise we're all commenting on the wrong bug right now.

[Daniel van Vugt (vanvugt)]

Judging by all the duplicate bugs and the global error reports (https://errors.ubuntu.com/problem/2248f9a7d43e5e9a3bba2ac8364590ed8b7361a7), this particular bug stopped happening with the introduction of gnome-shell version 3.26.1.

So if you continue to experience any problems, please open new bugs.

[Rocko (rockorequin)]

gnome-shell is definitely still crashing in Bionic whenever I turn off the only attached monitor, so I've opened bug #1742598 with one of the crash dumps it generated.

[Daniel van Vugt (vanvugt)]

Thanks. That is bug 1726352 so please discuss it in there.