Screen frozen after reboot. Xwayland crashed with fatal server error: (EE) wl_drm@4: error 0: authenicate failed

[Pascal Gicquel]

After I installed Ubuntu 19.04 (fresh install with hard drive erasing), I was able to login once just after install. But then after reboot, the screen freezes in the middle of the boot process and I never get the login banner.

I was able to launch the recovery mode and get some information through journalctl command and it seems that the problem is related to a Wayland server crash. I don't really know if the problem comes from Wayland or Gnome. The first worrying error message is : "gnome_shell[1165]: Failed to apply DRM plane transform 0: Permission non accordée" (ie, Permission denied in french)

Thanks to the recovery mode I was able to upgrade via "apt-get update" and "apt-get upgrade", but the symptoms were the same after a reboot

I uncommented the "Enable=true" flag of the [debug] section of /etc/gdm3/custom.conf and I provide and extract of the journalctl output related to the error as an attachment to this report (journalctl_extract.txt part). I also provide some system information (system.txt pat).

I hope this may help to solve the issue.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2019-07-15 (2 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: gdm3 3.32.0-1ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Tags: disco
Uname: Linux 5.0.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
mtime.conffile..etc.gdm3.custom.conf: 2019-07-18T07:25:10.575513

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1836805/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Jouni Mettala (jouni-mettala)]

Does it freeze if you boot with older kernel (linux-image) instead of recovery mode?

You can also try to uncomment WaylandEnable=false from /etc/gdm3/custom.conf to see if Xorg works better than Wayland.

[Daniel van Vugt (vanvugt)]

Please try the workaround in comment #3, and assuming that works please then run this command to send us more information about the system:

  apport-collect 1836805

[Pascal Gicquel (rogbro)]

apport information

[Pascal Gicquel (rogbro)]

apport information

[Pascal Gicquel (rogbro)]

apport information

[Pascal Gicquel (rogbro)]

A boot with 5.0.0-13 (available in boot menu after install) rather than default 5.0.0-20 provided the same symptoms.
I changed /etc/gdm3/custom.conf to boot with xorg and ... it did work.

I was able to run apport-collect.

I guess I will stay in this configuration. Don't hesitate to tell me if you need me to run more tests to help solving this issue

[Daniel van Vugt (vanvugt)]

Thanks. We will need to see more of the problem than the short extract provided so far:

==============================journalctl_extract.txt====================================
juil. 16 21:47:45 portable-ldlc gnome-shell[1165]: Failed to apply DRM plane transform 0: Permission non accordée
juil. 16 21:47:47 portable-ldlc gnome-shell[1165]: WL: error in client communication (pid 1165)
juil. 16 21:47:47 portable-ldlc org.gnome.Shell.desktop[1165]: (EE)
juil. 16 21:47:47 portable-ldlc org.gnome.Shell.desktop[1165]: Fatal server error:
juil. 16 21:47:47 portable-ldlc org.gnome.Shell.desktop[1165]: (EE) wl_drm@4: error 0: authenicate failed
juil. 16 21:47:47 portable-ldlc org.gnome.Shell.desktop[1165]: (EE)
juil. 16 21:47:48 portable-ldlc systemd[1]: systemd-hostnamed.service: Succeeded.
juil. 16 21:47:50 portable-ldlc gnome-shell[1165]: X Wayland crashed; exiting
...

Please reintroduce the bug and then collect the whole log from journalctl. If the bug has occurred during the current boot then run:

  journalctl -b0 > curboot.txt

Or if the problem occurred during the previous boot then run:

  journalctl -b-1 > prevboot.txt

and attach the resulting file.

Also, since "X Wayland crashed", please follow these instructions to help us track that down:

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

[Pascal Gicquel (rogbro)]

Generated the prevboot.txt (see attached). I did not find any file related to wayland crash in /var/crash. I did find though an xorg crash file dated from this morning. I sent it through ubuntu-bug though I was not asked a bug number (I am not sure it worked). I do not really understand what happened this morning as the xorg config ended up working. I don't know if this new fact may help solving the issue or is rather disturbing...

[Daniel van Vugt (vanvugt)]

Please go to step 2 in:

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

[Pascal Gicquel (rogbro)]

Back to my computer

I applied step 2 as suggested and got :

whoopsie-id: e3a8dbc9dbb2e9589754eb397d8ff19924a7bec147827c8e2333de7493dcd433a7cacae13de6185804843502331b4626bb6de5038cc1a182ec3b3aa4ed9c2130

which give the following line:
2019-07-18 07:07 2019-07-19 20:07 UTC Crash xserver-xorg-core with the link: https://errors.ubuntu.com/oops/8d8b8168-aa67-11e9-b233-fa163e102db1

I will now try step 4 but have to reboot with wayland...

[Daniel van Vugt (vanvugt)]

I wonder if you have a stale monitors.xml that's incurring the:

  Failed to apply DRM plane transform 0: Permission non accordée

Please try removing: ~/.config/monitors.xml
and then reboot.