[regression] Login screen flickers to black a few times on boot and then finally settles on using Xorg instead of Wayland. No Wayland login option.

Bug #1786883 reported by Daniel van Vugt
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
Fix Released
High
Unassigned

Bug Description

https://gitlab.gnome.org/GNOME/mutter/issues/264

---

The cosmic login screen flickers to black a few times on boot and then finally settles on using Xorg instead of Wayland.

I can tell because from ssh user 'gdm' is running:

/usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3

and not the usual Xwayland. Also the login screen offers no choice of Xorg or Wayland sessions.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gdm3 3.29.91-1ubuntu1
ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9
Uname: Linux 4.17.0-6-generic x86_64
ApportVersion: 2.20.10-0ubuntu7
Architecture: amd64
Date: Tue Aug 14 11:41:31 2018
InstallationDate: Installed on 2018-05-26 (79 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Changed in gdm3 (Ubuntu):
importance: Undecided → High
Changed in mutter (Ubuntu):
importance: Undecided → High
tags: added: regression
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

In both cases I see:

Aug 14 11:40:46 kab gnome-shell[890]: X Wayland crashed; exiting

Aug 14 11:49:16 kab gnome-shell[890]: X Wayland crashed; exiting

which would explain why the Wayland option is missing when I finally get a login screen.

Unfortunately there are no crash files or core dumps :(

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
summary: [regression] Login screen flickers to black a few times on boot and then
- finally settles on using Xorg instead of Wayland
+ finally settles on using Xorg instead of Wayland. No Wayland login
+ option.
Revision history for this message
Iain Lane (laney) wrote :

Please could you file upstream? Ray landed some re-working of VT handling and the lifecycle of the GDM greeter and it's possible some bugs still exist there.

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

That probably explains bug 1786872 more than this one.

I'll try collecting some more information first, especially since XWayland not leaving core files is a mutter fix I already own.

Revision history for this message
Iain Lane (laney) wrote :

If you file it, the output in the journal might already indicate a problem that can be fixed.

If you don't, no fix will happen.

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

Downgrading to gdm3 3.29.90 somewhat avoided the problem and reverted to bug 1786872. But when VT switching to work around that one I managed to reproduce this crash again, even with gdm3 3.29.90-2ubuntu1.

Finally got a crash report from Xwayland this time -> bug 1786914

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

And another log. I think grepping for the gnome-shell PID that owned the failed Xwayland instance might be a helpful way to read the logs...

Aug 14 17:29:17 kab /usr/lib/gdm3/gdm-wayland-session[870]: gnome-session-binary[876]: DEBUG(+): GsmAutostartApp: started pid:886
Aug 14 17:29:17 kab gnome-session-binary[876]: DEBUG(+): GsmAutostartApp: started pid:886
Aug 14 17:29:17 kab gnome-shell[886]: Failed to apply DRM plane transform 0: Permission denied
Aug 14 17:29:17 kab gnome-shell[886]: WL: error in client communication (pid 886)
Aug 14 17:29:17 kab org.gnome.Shell.desktop[886]: (EE)
Aug 14 17:29:17 kab org.gnome.Shell.desktop[886]: Fatal server error:
Aug 14 17:29:17 kab org.gnome.Shell.desktop[886]: (EE) wl_drm@4: error 0: authenicate failed
Aug 14 17:29:17 kab org.gnome.Shell.desktop[886]: (EE)
Aug 14 17:29:18 kab gnome-shell[886]: X Wayland crashed; exiting
Aug 14 17:29:18 kab /usr/lib/gdm3/gdm-wayland-session[870]: gnome-session-binary[876]: DEBUG(+): GsmAutostartApp: (pid:886) done (status:1)
Aug 14 17:29:18 kab gnome-session-binary[876]: DEBUG(+): GsmAutostartApp: (pid:886) done (status:1)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
no longer affects: mutter (Ubuntu)
Changed in gdm3 (Ubuntu):
status: New → Triaged
tags: added: fixed-in-gdm-3-29.92
tags: added: fixed-in-gdm-3.29.92
removed: fixed-in-gdm-3-29.92
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

gdm3 (3.30.0-0ubuntu1) cosmic; urgency=medium

  * Updated to 3.30.0 release:
    - build fixes
    - search for sessions in XDG_DATA_DIRS
    - blacklist some more wayland unfriendly hardware
    - initial setup fix
    - flicker fix
    - misc bug fixes
  * debian/gdm3.install:
    - install udev rules in the correct folder (following upstream build
      fixes)

 -- Didier Roche <email address hidden> Wed, 05 Sep 2018 11:20:11 +0200

Changed in gdm3 (Ubuntu):
status: Triaged → Fix Released
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.