After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 786660 - 3.25.91: Unable to log in: invalid monitor configuration, Logical monitors not adjecent
3.25.91: Unable to log in: invalid monitor configuration, Logical monitors no...
Status: RESOLVED OBSOLETE
Product: mutter
Classification: Core
Component: general
3.25.x
Other Linux
: Normal critical
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2017-08-23 01:21 UTC by Jeremy Bicha
Modified: 2021-07-05 13:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
monitors.xml (3.80 KB, text/xml)
2017-08-23 01:21 UTC, Jeremy Bicha
Details

Description Jeremy Bicha 2017-08-23 01:21:33 UTC
Created attachment 358188 [details]
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.
Comment 1 Jeremy Bicha 2017-08-23 01:26:30 UTC
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.
Comment 2 Jonas Ådahl 2017-08-23 02:26:06 UTC
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.
Comment 3 Jeremy Bicha 2017-08-23 12:13:57 UTC
(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.
Comment 4 Jonas Ådahl 2017-08-29 13:02:45 UTC
(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
Comment 5 GNOME Infrastructure Team 2021-07-05 13:43:32 UTC
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.