'Ubuntu' starts an x11 session instead of wayland

[Jean-Baptiste Lallement]

artful desktop up to date on real hardware

Test Case
1. In gdm select a user
2. Click on the cog
  -> Verify the list of sessions available
4. Select "Ubuntu" and log in
  -> Verify that wayland is running ($WAYLAND_DISPLAY is set)

Expected Result
At least "Ubuntu" and "Ubuntu on Xorg" are available
Wayland is running

Actual result
Both entries start xorg instead of wayland. Sometimes it's the opposite, both entries start wayland.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-session (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 31 18:59:31 2017
InstallationDate: Installed on 2013-09-03 (1457 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

[Sebastien Bacher (seb128)]

Thanks, is it doing it after a reboot? One theory could be that when the session files on disk change then gdm doesn't refresh its index and things get confused

[Jean-Baptiste Lallement (jibel)]

I ran the following test:

1. Boot your system
2. Select Xorg
  -> Xorg session starts
3. Logout and select Wayland
  -> Wayland session starts
4 Logout and select Xorg
  -> FAIL: Wayland session starts

I'll try the other way around but it seems to confirm you theory that it works on a fresh boot and then gdm gets confused.

[Khurshid Alam (khurshid-alam)]

It's exactly opposite to me.

There are two session

1)Ubuntu and

2) Ubuntu-on-wayland

Ubuntu boots into wayland (no .xauthority) and Ubuntu-on-wayland fails to load. Where is xorg session?

[Jean-Baptiste Lallement (jibel)]

I confirm comment #3, after a fresh boot, the session selected is correctly started, then this session will be used for any subsequent logout/login whichever entry is selected in gdm.

[Sebastien Bacher (seb128)]

I don't see the issue described in comment #3 here, the previous comment is always confusing since it states "then this session will be used for any subsequent logout/login whichever entry is selected in gdm." but in

"1. Boot your system
2. Select Xorg
  -> Xorg session starts
3. Logout and select Wayland
  -> Wayland session starts"

so the first session is not used for subsequent logins, or is that the second one?

I wonder if it could have to do with https://bugzilla.gnome.org/show_bug.cgi?id=785918 ... could you go to a vt and stop the pulseaudio processes before logging in an see if that makes a difference?

[Jean-Baptiste Lallement (jibel)]

I mean, if, after boot, I select wayland, then on next logins, the wayland session always starts whether I select X or Wayland.
The same happens the other way around, if, after boot, I select xorg, then on next logins, the xorg session always starts whether I select X or Wayland.

It is reproducible on real hardware, regularly upgraded, and in a freshly installed VM.

I'll check if stopping pulseaudio makes a different.

[Daniel van Vugt (vanvugt)]

We're discussing this in bug 1705157 instead. If you can find a better title for it then feel free to reword :)