17.10 Login To Wayland Fails Unless User Logs Into Unity First

Bug #1726192 reported by Rick Grundy on 2017-10-23
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-desktop (Ubuntu)

Bug Description

After upgrading from 17.04 to 17.10, it's not possible to log into the default 'Ubuntu' session unless I log into Unity first. If I log into Unity, immediately log out, then log into Ubuntu, it logs in without issue.

If I don't log into Unity first, the login attempt to Ubuntu briefly shows a black screen, then returns immediately to the login prompt.

From suspend or hibernate, I can continue using the Wayland session without issue through poweroff. If I reboot or shutdown, the first login needs to be Unity, then I can log out and back to the Ubuntu session normally.

Attached is some output from syslog showing gnome-session related errors. I'm not sure if they show the specific error, but they do appear at the time a first Ubuntu login is attempted.

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/1726192/+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.]

tags: added: bot-comment
dino99 (9d9) wrote :

Confirmed on a fresh mini.iso install:
-gdm3 fails (login loop) to open a wayland session (both gnome & ubuntu)
- installing lightdm (which has some unity dependencies) allow to open a wayland session

Launchpad Janitor (janitor) wrote :

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

Changed in ubuntu:
status: New → Confirmed
dino99 (9d9) on 2017-10-23
tags: added: artful gdm3 wayland
affects: ubuntu → gnome-desktop (Ubuntu)
Sebastien Bacher (seb128) wrote :

That's a pretty weird bug. Could you give details on your video cards/drivers? Also enable gdm debugging by uncommenting the debug line in /etc/gdm3/custom.conf and reboot, try to log into a wayland session and then add your syslog?

Changed in gnome-desktop (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete

My system uses Intel graphics and the default driver. The graphics details are below:

       description: VGA compatible controller
       product: Crystal Well Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 08
       width: 64 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:30 memory:f7800000-f7bfffff memory:e0000000-efffffff ioport:f000(size=64) memory:c0000-dffff

Also, attached is the complete syslog file with GDM debugging enabled captured from the terminal immediately following a failed Wayland login, prior to going through the Unity login steps. Thanks.

Sebastien Bacher (seb128) wrote :

syslog has
gdm-wayland-session: Unable to load file '/etc/gdm3/custom.conf': Key file contains line “More verbose logs” which is not a key-value pair, group, or comment

it looks like you edited it incorrectly?

My fault. A little to quick to hit 'x' in vi. Attached is a new syslog file that should have debug properly enabled.

Changed in gnome-desktop (Ubuntu):
status: Incomplete → New
Traumflug (mah-jump-ing) wrote :

Good catch. The description of the behavior is very similar. Following a review of that thread, I did some more testing. Below are the findings:

Reboot the system
Attempt to log into 'Ubuntu' session
  Screen goes black for 2-3 seconds and returns me to login screen
Attempt to log into 'Ubuntu on Xorg' session
  Login succeeds and session starts normally
Log out
Attempt to log into 'Ubuntu' session
  Screen goes black for 2-3 seconds and returns me to login screen
Attempt to log into 'Unity' session
  Login succeeds and Unity session starts normally
Log out
Attempt to log into 'Ubuntu' session
  Login succeeds and session starts normally

So, it appears that I can log into either Unity or Ubuntu on Xorg after a clean reboot without issue. However, I can only log into a Ubuntu session if I have first logged into a Unity session, then logged out. Logging in to Xorg doesn't help.

Attached is a new debug syslog that should capture the entire sequence. The login attempts should start at the 'Oct 25 15:32:39' timestamp.

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

Other bug subscribers