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))
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Shell |
Fix Released
|
Medium
|
|||
Mutter |
Fix Released
|
Medium
|
|||
gnome-shell (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
mutter (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
https:/
---
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
ProcVersionSign
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)
Related branches
Changed in mutter: | |
importance: | Unknown → Critical |
status: | Unknown → Confirmed |
Changed in mutter: | |
status: | Confirmed → Fix Released |
Changed in mutter: | |
importance: | Unknown → Critical |
status: | Unknown → Confirmed |
Changed in mutter (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in gnome-shell (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in gnome-shell: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
Changed in mutter: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
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. _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'.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/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.