GNOME: Unable to log in: invalid monitor configuration, Logical monitors not adjecent

[Nicolás Abel Carbone]

After updating to gnome 3.25.91, and now testing in 3.26, I cannot login to wayland session, either ubuntu o vanilla gnome. Xorg session works fine, and wayland session worked fine before updating.

The only error I can detect in the logs is "Unrecoverable failure in required component org.gnome.Shell.desktop".

journal excerpt
===============
Aug 22 21:12:31 gnome-shell[23153]: Ignoring invalid monitor configuration for LVDS1:LGD:0x02f8:0x00000000, VGA1:???:0x0000:0x00000000: Logical monitors not adjecent
Aug 22 21:12:32 kernel: gnome-shell[23153]: segfault at 8 ip 00007f5a7c06ebd0 sp 00007ffdc85ce7c8 error 4 in libmutter-1.so.0.0.0[7f5a7c015000+13e000]

Workaround
==========
Move or remove the hidden file ~/.config/monitors.xml to be able to log in to GNOME Shell.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 18 09:44:01 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-07-27 (52 days ago)
InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

[Jeremy Bícha (jbicha)]

Created attachment 358188
monitors.xml

Ubuntu 17.10 Alpha

I built gnome-settings-daemon, mutter and gnome-shell 3.25.91 for upload to Ubuntu. I rebooted and tried to log in with my new packages (I had been using 3.25.90 before). GDM showed up but logging in to GNOME didn't work.

journal excerpt
===============
Aug 22 21:12:31 gnome-shell[23153]: Ignoring invalid monitor configuration for LVDS1:LGD:0x02f8:0x00000000, VGA1:???:0x0000:0x00000000: Logical monitors not adjecent
Aug 22 21:12:32 kernel: gnome-shell[23153]: segfault at 8 ip 00007f5a7c06ebd0 sp 00007ffdc85ce7c8 error 4 in libmutter-1.so.0.0.0[7f5a7c015000+13e000]

Workaround
==========
After moving or removing ~/.config/monitors.xml I was able to log in.

I'm attaching a copy of my monitors.xml file that mutter 3.25.91 couldn't handle but worked fine with 3.25.90.

[Jeremy Bícha (jbicha)]

I believe I had copied my ~/.config/monitors.xml from one or two previous computers. Currently, I don't use any external monitors with my laptop.

[Jonas Ådahl (jadahl)]

Could you provide a backtrace? I can't reproduce any crash when using your monitors.xml, I only see the "not adjecent" error, then everything works anyway.

[Jeremy Bícha (jbicha)]

(In reply to Jonas Ådahl from comment #2)
> Could you provide a backtrace? I can't reproduce any crash when using your
> monitors.xml, I only see the "not adjecent" error, then everything works
> anyway.

Could you show me how to do that? Ubuntu's apport did not automatically catch a backtrace for gnome-shell/mutter.

[Jonas Ådahl (jadahl)]

(In reply to Jeremy Bicha from comment #3)
> (In reply to Jonas Ådahl from comment #2)
> > Could you provide a backtrace? I can't reproduce any crash when using your
> > monitors.xml, I only see the "not adjecent" error, then everything works
> > anyway.
>
> Could you show me how to do that? Ubuntu's apport did not automatically
> catch a backtrace for gnome-shell/mutter.

I don't know how to do it in Ubuntu. Maybe this page can help: https://wiki.ubuntu.com/Backtrace

[Sebastien Bacher (seb128)]

Thank you for your bug report, is that on real hardware or in a vm? What videocard/driver do you use? Do you get any report in /var/crash?

[Nicolás Abel Carbone (nicocarbone)]

This is on real hardware. I am using an hybrid Intel Ironlake Mobile / AMD Redwood notebook. It should boot using the Intel GPU.

I have a old crash report in var/crash. I think it is from before the update from 3.25.91 to 3.26.0, I attach it here.

[Nicolás Abel Carbone (nicocarbone)]

Just to be clear: the previous is an old (from last wednesday) crash that happened when trying to enter the wayland session. In that time, after I logged on xorg, a crash report appeared.
Since then, in all my last tries, wayland session login failed silently, without a crash report.

[Jeremy Bícha (jbicha)]

Please try moving your ~/.config/monitors.xml file somewhere else. This sounds like https://bugzilla.gnome.org/786660

[Nicolás Abel Carbone (nicocarbone)]

Thank you Jeremy! That did the trick! It seems it is that same bug.
Should I mark this bug report as duplicated of some other?

[Jeremy Bícha (jbicha)]

Nicolás, this is the first bug reported for this issue in Launchpad that I am aware of so there's no need to mark this as a duplicate.

[Marco Trevisan (Treviño) (3v1n0)]

So the commit https://github.com/GNOME/mutter/commit/43eeb009ce78588db9fba48574f377629d5de1aa avoids invalid configurations to be migrated. As for the crash nor me or Jonas can reproduce it.

I've tried to get informations from the coredump, but it doesn't contain any information about the packages versions, so I can't get the proper stacktrace out of it.

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

[Stewart Seidel (sgseidel)]

I am seeing an issue with mutter-2 in Ubuntu 18.04, a fresh installation on Virtualbox 6.08. The host machine is a Mac Pro on macOS 10.14.5 Mojave.

Here is a link to a thread I opened on LinuxQuestions.org with additional details:

https://www.linuxquestions.org/questions/linux-newbie-8/ubuntu-18-04-2-login-screen-unavailable-after-livepatch-applied-4175656235-new/

If I can be of any additional assistance please let me know.

[Daniel van Vugt (vanvugt)]

Bug kept open based on Stewart's comment #10.

[Daniel van Vugt (vanvugt)]

This looks like an issue that was fixed in 20.04 this year. Can anyone confirm if it still happens on a fully updated 20.04 system?

[Gnome-sysadmin (gnome-sysadmin)]

GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/mutter/-/issues/

Thank you for your understanding and your help.

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.

Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it anymore. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.