Default session reverted to Xorg

[Dean Henrichsmeyer]

I have been using Wayland for some time. In a recent artful update, my session reverted to Xorg causing all sorts of HiDPI scaling issues (see https://bugs.launchpad.net/bugs/1714295).

Even though in the gdm3 options Ubuntu (default Wayland) was selected, it was using Xorg. In order to get back to using wayland for my session I had to select Xorg, then select Ubuntu default again. Once I did that and logged in, it was using wayland properly again.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gdm3 3.25.90.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 8 11:21:17 2017
InstallationDate: Installed on 2017-07-23 (46 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
ProcEnviron:
 TERM=xterm
 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)

[Brad Figg (brad-figg)]

I experienced the same issue and fixed in the same way.

[Launchpad Janitor (janitor)]

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

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1705157, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.