[nouveau] Login screen seems to be crashing with multiple monitors (6720x1050 from 4x 1680x1050)

Bug #1836278 reported by Len Rose
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Boot process halts at the point it normally runs gdm, it seems to keep re-trying. I learned that if I turn off the third and fourth monitor it will successfully run the desktop without crashing on the first two monitors. Once desktop (X) is fully operational, I can turn on third and fourth monitor and the workspace is initialized and I have (4) working monitors. I have never reported a bug before please excuse any faux pas. Best Regards, and wanted to say Thanks! for all the wonderful and amazing software.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.3-0ubuntu18.04.4
ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 11 18:36:14 2019
InstallationDate: Installed on 2019-01-10 (182 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Len Rose (terminus00) wrote :
Revision history for this message
Len Rose (terminus00) wrote :

I forgot to mention I downgraded gdm first to try and solve the issue but it did not change the problem. I intend to re-install latest again but wanted to file the report first.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please run these commands (with all monitors turned on):

lspci -k > lspcik.txt
xrandr > xrandr.txt
dpkg -l > allpackages.txt
journalctl -b0 > journal.txt

and then attach the resulting four text files to this bug.

Changed in gdm3 (Ubuntu):
status: New → Incomplete
Revision history for this message
Len Rose (terminus00) wrote :

Additional information attached as requested! Thanks

Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: GDM seems to be crashing with multiple monitors (6720x1050 from 4x 1680x1050)

Thanks.

"it seems to keep re-trying" indeed suggests something is crashing, so to report a crash please follow these instructions:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

The process that would be crashing even for the login screen is called 'gnome-shell'.

tags: added: nouveau
summary: - GDM seems to be crashing with multiple monitors
+ GDM seems to be crashing with multiple monitors (6720x1050 from 4x
+ 1680x1050)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Finally, as a workaround please try uncommenting:

  #WaylandEnable=false

in /etc/gdm3/custom.conf, and then reboot.

summary: - GDM seems to be crashing with multiple monitors (6720x1050 from 4x
- 1680x1050)
+ [nouveau] Login screen seems to be crashing with multiple monitors
+ (6720x1050 from 4x 1680x1050)
Revision history for this message
Len Rose (terminus00) wrote :

The workaround is splendid! Both display cards and all 4-monitors are initializing at boot with the splash screen appearing early, all displays are functioning normally. Thank you very much! I have uploaded (2) crash files from 0835MDT when I rebooted today. One was for gnome-shell and one was for uXwayland. I am not sure why but there were no later crashes despite failing to bring up gdm as it booted. Thanks very much for the help.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

If your uploaded crash files resulted in new bugs being opened then please tell us the new bug IDs.

Otherwise, please do step 2 from comment #5:

Look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

Revision history for this message
Len Rose (terminus00) wrote :

Initially that whoopsie id wasn't registering using that system... However I tried it again and it is working now. https://errors.ubuntu.com/user/23a4afcb50334ac883e539750fe49827a6831f9da843f7672bdfc1335dd995623c3a68792f935aaa49ff49e39ac68d51baa34a223ecc292aa6c1293d302ebd8f shows a great deal of crash reports.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Perfect, thanks.

I have turned your crash report into a new bug 1836290, so we will use that one now.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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