gnome-shell crashes with meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed

[Adam Fussell]

I have a kaby lake nuc (NUC7i5BNK) connected to a Samsung 4K tv over hdmi. If i turn the TV off, when i switch it back on, the session is killed and I'm sent back to the login screen.

Occurs on 17.10 and 18.04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: mutter 3.27.92-1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Fri Mar 9 15:02:50 2018
InstallationDate: Installed on 2017-12-01 (98 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: mutter
UpgradeStatus: Upgraded to bionic on 2018-03-09 (0 days ago)

[Adam Fussell (adamfussell)]

Log excerpt:

Mar 09 13:56:16 pig gnome-shell[1171]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
Mar 09 13:56:16 pig gnome-shell[1171]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed
Mar 09 13:56:16 pig gnome-shell[1171]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
Mar 09 13:56:16 pig gnome-shell[1171]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed
Mar 09 13:56:16 pig gnome-shell[1171]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
Mar 09 13:56:16 pig gnome-shell[1171]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed

[Launchpad Janitor (janitor)]

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

[Daniel van Vugt (vanvugt)]

This is fixed in gnome-shell 40.1 apparently https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1810

[bluppfisk (bluppfisk)]

Hello Daniel, coming over here as requested from the other bug (1952766).

Two questions:

1. How can you tell from that page that the code change has arrived in 40.1? I can only see when it was merged, but am unable to tell whether this particular fix is in that version.

2. Since I'm on gnome-shell version 40.5, it seems this is either a regression or the fix has gone somewhere else?

```
~$ gnome-shell --version
GNOME Shell 40.5
```

[Daniel van Vugt (vanvugt)]

40.1 is the first tag in gnome-shell's git that came after the fix 1f0ef7fb4692f8ad6a040567f29097e0c3688e52...

I feared you might say you're already on a higher version. In that case please continue the conversation in bug 1952766.

[Pierre A (palba-deactivatedaccount-deactivatedaccount)]

I have this error also in GNOME Shell 45.3.

I often occurs after suspend while 4K external monitor is connected.

[Dalyn Dalton (itsthenewdx2)]

It appears that this has been fixed in the upstream
https://gitlab.gnome.org/GNOME/mutter/-/issues/3402#note_2070469

[Daniel van Vugt (vanvugt)]

Since this bug was fixed a few years ago, let's keep the new issue in bug 2065632.