With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input [gnome-shell: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: No matching EGL configs]

[Erick Brunzell]

Just testing Disco and wanted to see what login options are available after adding 'gnome-shell-extensions' and found that logging out lands me on a black screen that's unresponsive to any keyboard input. I'll test on some slightly different hardware soon.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gdm3 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 12 16:18:56 2019
InstallationDate: Installed on 2019-04-12 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
ProcEnviron:
 TERM=xterm-256color
 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)
mtime.conffile..etc.gdm3.custom.conf: 2019-04-12T01:05:45.138523

[Erick Brunzell (lbsolost)]

I found that turning auto-login off resulted in booting to a black screen so after unsuccessfully trying the nomodeset boot option I installed 'lightdm-gtk-greeter' and 'lightdm' from recovery mode which gives me a working system. I had encountered no problems with desktop behavior but this box has Intel GMA X4500 graphics (old-ish I know) so I wonder if it could be related to bug #1727356?

Having installed 'gnome-shell-extensions' package from the repos I'm able to boot and run all three available sessions - Ubuntu, Ubuntu w/Wayland, and "Classic" with no apparent issues as long as I use lightdm instead of gdm3.

[Erick Brunzell (lbsolost)]

This does appear to be hardware related because I encounter no problem on a box with Intel G41 graphics but the X4500 is a no-go with gdm3.

[Erick Brunzell (lbsolost)]

Slight change in behavior testing a fresh install of 20190413.2 - if installed with auto-login switched on logout did load and give the expected choices of Ubuntu and Ubuntu w/Wayland. But if auto-login is turned off I still get a black screen on reboot. I suspect that gdm3 is not even loading because I've tried blindly opening a tty, logging in as root, and sudo reboot but nothing happens.

Once again just installing lightdm (I haven't tried the old unity-greeter) gives me a working machine. By looking at the changelog nothing has changed in gdm3 so I'm unsure why the logout behavior would have improved with a fresh install??????????

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1824588

[Daniel van Vugt (vanvugt)]

Please:

1. Run:

   lspci -k > lspcik.txt

   and send us the file 'lspcik.txt'.

2. Reproduce the black screen problem, reboot and then run:

   journalctl -b-1 > prevboot.txt

   to collect the log of the previous boot which had the problem, and send us the file 'prevboot.txt'.

[Daniel van Vugt (vanvugt)]

This might also be related to bug 1819943.

[Erick Brunzell (lbsolost)]

As requested. Definitely C2D era board (Intel DG43GT) running a Pentium Dual Core.

[Erick Brunzell (lbsolost)]

Method used to collect this info:

(1) Fresh installed 20190413.2 choosing not to auto-login.
(2) Rebooted after install and surprisingly gdm3 appeared as it should so I booted to desktop and just rebooted.
(3) That reboot failed as had been the previous case - just a black screen, totally unresponsive.
(4) Performed a hard reboot with the reset button on the PC, entered recovery from grub menu, then installed lightdm, and rebooted.
(5) Collected info as instructed.

So there are a total of 3 boots. The first was successful - no problems. The second booted to a black screen instead of displaying gdm3 screen. Third boot was performed using lightdm.

[Daniel van Vugt (vanvugt)]

Thanks. Unfortunately that log is not helpful because it contains only one boot done in recovery mode with modesetting disabled:

Apr 15 14:33:53 lance-desktop kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic root=UUID=ddacea78-cdda-4236-94c3-4c4d9d3dad20 ro recovery nomodeset

Please reproduce the black screen problem once (ensuring that you are not booting into recovery mode*), then reboot again once, and then run:

   journalctl -b-1 > prevboot.txt

to collect the log of the previous boot which had the problem, and send us the file 'prevboot.txt'.

* To ensure you are not booting in recovery mode, as soon as the purple screen appears tap Escape. Then search through the menus and choose a kernel to boot that is not recovery mode.

[Erick Brunzell (lbsolost)]

This was tricky but I finally got a successful boot (following several failed boots) using gdm3 by selecting the kernel with "e" from grub and then removing 'quiet splash'. So I hope this is more helpful.

[Erick Brunzell (lbsolost)]

Based on those most recent results I ran "dpkg-reconfigure grub-pc" and removed "quiet splash". Now it boots to the gdm3 screen every time. So maybe something to do with how plymouth hands off the boot process to gdm3? Or how quickly that hand off is completed?

[Daniel van Vugt (vanvugt)]

Thanks. This appears to be the most interesting part of the log I can see:

Apr 15 22:22:50 lance-desktop gnome-shell[865]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: No matching EGL configs
Apr 15 22:22:50 lance-desktop gnome-shell[865]: Failed to apply DRM plane transform 0: Permission denied
Apr 15 22:22:51 lance-desktop gnome-shell[865]: WL: error in client communication (pid 865)
Apr 15 22:22:51 lance-desktop org.gnome.Shell.desktop[865]: (EE)
Apr 15 22:22:51 lance-desktop org.gnome.Shell.desktop[865]: Fatal server error:
Apr 15 22:22:51 lance-desktop org.gnome.Shell.desktop[865]: (EE) wl_drm@4: error 0: authenicate failed
Apr 15 22:22:51 lance-desktop org.gnome.Shell.desktop[865]: (EE)
Apr 15 22:22:51 lance-desktop nm-dispatcher[734]: req:4 'connectivity-change': start running ordered scripts...
Apr 15 22:22:51 lance-desktop nm-dispatcher[734]: req:5 'dhcp6-change' [enp0s25]: start running ordered scripts...
Apr 15 22:22:51 lance-desktop gnome-shell[865]: X Wayland crashed; exiting
Apr 15 22:22:52 lance-desktop gnome-session[858]: gnome-session-binary[858]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Apr 15 22:22:52 lance-desktop gnome-session-binary[858]: Unrecoverable failure in required component org.gnome.Shell.desktop
Apr 15 22:22:52 lance-desktop gnome-session-binary[858]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Apr 15 22:22:52 lance-desktop systemd-logind[529]: Failed to restore VT, ignoring: Input/output error

So next please follow these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

[Erick Brunzell (lbsolost)]

Sadly /var/crash is empty, and errors.ubuntu.com + whoopsie-id just displays a blank page. Also applying the workaround from bug 994921 does not result in creating a crash report.

I started testing Ubuntu Disco 20190416 tonight and knowing what I know now I can say with certainty that the easiest way to reproduce this bug (on effected hardware) is to perform a fresh install choosing NOT to auto-login.

Then the first boot will be OK but each subsequent boot will produce a black screen - that is the gdm3 login screen never appears and it's not possible to enter a TTY. But once "quiet splash" is removed via grub the system boots as it should.

[Daniel van Vugt (vanvugt)]

That sounds like a different bug; the login screen never appearing. Although both bugs might end up benefiting from a single fix.

I wonder if you could log that as a new bug, so that other people experiencing the same symptoms don't get confused?...

> Then the first boot will be OK but each subsequent boot will produce a black screen - that is the gdm3 login screen never appears and it's not possible to enter a TTY. But once "quiet splash" is removed via grub the system boots as it should.

[Erick Brunzell (lbsolost)]

I will follow up ASAP. The plot continues to thicken. I tried a different set of hardware today with a B43 chipset and it didn't seem to be effected. But that board has only DVI and VGA outputs whereas the effected board with a G43 chipset has DVI and HDMI. I'd been using HDMI so now I ran another range of tests using DVI on the effected board and was unable to reproduce.

So this appears to effect a very selective subset of 10 to 12 year old hardware. Must be Intel X4500 graphics with HDMI connection and possibly only the G43 chipset. So it's the absolute corneriest of corner issues I've ever encountered. And the workaround couldn't be any simpler - just remove the "quiet splash" boot parameter and all seems well (both boot to and logout to gdm3 screen).

BTW ASAP may be rather slow in coming because I have a few medical procedures scheduled in the next few weeks.

[Daniel van Vugt (vanvugt)]

This problem is probably related to:

"Following Mutter's 3.32.1 release, meanwhile, the developers have now hard-enforced a requirement that graphics drivers on the system either support OpenGL 2.1 or OpenGL ES 2.0 as a minimum."

[https://www.phoronix.com/scan.php?page=news_item&px=GNOME-Shell-Mutter-3.32.1]

Although Mesa offers software rendering which supports newer OpenGL. Therefore gdm3 and mutter *should* be detecting that the GPU is too old and falling back. It's a semi-regular problem though, that gdm3 and mutter fail to fall back reliably and the login screen never appears.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

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.

[naisanza (naisanza)]

`sudo killall -9 gdm` immediately fixes the "unresponsive" problem for me. But you have to SSH into the box to do this, which is an extreme bandaid

The screen remains blank even moving the mouse around for a few minutes, and pressing ESC a couple times.

The monitor shows as "no input"