gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number: assertion failed: ((unsigned int) number < g_list_length (manager->logical_monitors))

Bug #1717170 reported by ryzko on 2017-09-14
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mutter
Confirmed
Critical
mutter (Ubuntu)
High
Unassigned

Bug Description

I'm testing Ubuntu 17.10 installed on Lenovo PC (with Intel Core i5-6500 CPU and Intel HD Graphics 530 (skylake GT2). Session is crashing (login screen is displayed again) every time I change the monitor Input (e.g. from DP to HDMI) or switching off the monitor. It is happening since some updated from beginning of September were installed. Same situation is for both session types, default Wayland and also for X.org. Tested also with Live USB, same behaviour.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.25.91-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 14 07:28:54 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-09-11 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

ryzko (ryzko) wrote :
Daniel van Vugt (vanvugt) wrote :

Sounds like you might have hit bug 1714330 but we should go though the proper procedure in case you're experiencing a different problem...

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
ryzko (ryzko) wrote :

Apport is enabled in /etc/default/apport but no file is located /var/crash even after crash. I have created the bug report using ubuntu-bug tool.

ryzko (ryzko) wrote :

Please how to force .crash file creation?

Daniel van Vugt (vanvugt) wrote :

Have a look in your /var/crash/

If there are none there already then I'm not sure why, other than dumping of core somehow failed, or less likely it's not "crashing" via any of the normal fatal signals.

ryzko (ryzko) wrote :

Hello. /var/crash/ is empty. I have attached part of Syslog starting at the time I switched off the monitor and a lot of errors were logged since that time. Please look at it, may be it can help also determine why crash file is not generated.

Daniel van Vugt (vanvugt) wrote :

Thanks. Your log shows gnome-shell is crashing in libmutter:

Sep 13 14:08:10 internet-ws kernel: [11508.541040] gnome-shell[3056]: segfault at 2c ip 00007fd7c9d0cb24 sp 00007ffc4ffe2a28 error 4 in libmutter-1.so.0.0.0[7fd7c9c6f000+13f000]
Sep 13 14:08:10 internet-ws gnome-session[2964]: gnome-session-binary[2964]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Sep 13 14:08:10 internet-ws gnome-session-binary[2964]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11

So it does sound like this might be bug 1714330. Please fully update your system and tell us if the problem persists.

ryzko (ryzko) wrote :

The system is up to date. Unfortunately the problem persist.
I'm Sorry, I have added old syslog file in previous post. Please find attached syslog from today morning, logs starting on the time of crash.

Daniel van Vugt (vanvugt) wrote :

Aha!

Yes you were probably experiencing bug 1714330 in the old log of comment #6 but not any more.

In your new log of comment #8 you are now experiencing a new assertion:

Sep 18 07:25:39 internet-ws org.gnome.Shell.desktop[1891]: mutter:ERROR:backends/meta-monitor-manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number: assertion failed: ((unsigned int) number < g_list_length (manager->logical_monitors))

... preceded by Javascript errors about the primary monitor.

Please try deleting this file in your home directory:

  ~/.config/monitors.xml

and then reboot.

Changed in gnome-shell (Ubuntu):
status: Incomplete → New
summary: - Gnome-shell session crash after monitor switch-off/input change.
+ gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-
+ manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number:
+ assertion failed: ((unsigned int) number < g_list_length
+ (manager->logical_monitors))
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
ryzko (ryzko) wrote :

hmm, no such file ~/.config/monitors.xml in my home directory

Daniel van Vugt (vanvugt) wrote :

I mean "~" is your home directory, ".config" is a directory and "monitors.xml" is the file. :)

Regardless, your original description suggests the invalid config occurs dynamically. Not necessarily on disk.

affects: gnome-shell (Ubuntu) → mutter (Ubuntu)
Changed in mutter (Ubuntu):
status: Incomplete → Confirmed
Daniel van Vugt (vanvugt) wrote :

Found it. Gnome Developers are already aware of the crash:
https://bugzilla.gnome.org/show_bug.cgi?id=787637

If you would like to contribute to a speedy resolution then please comment on that page.

Changed in mutter (Ubuntu):
importance: Undecided → High
ryzko (ryzko) wrote :

Thank you, yes It seems that the bug report you found on Gnome Bugzilla is reporting the same type of crash.

Changed in mutter:
importance: Unknown → Critical
status: Unknown → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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