Bug#866758: upgrade-reports: Gnome3 boots only to Wayland session
Package: upgrade-reports
Followup-For: Bug #866758
Following the Debian upgrade below, GDM3 boots to a blank *graphical desktop* when Default X11 login is selected. Desktop shuts down automatically after several minutes, (usually.)
The cursor is active at login prompt, then disappears if 'System X11 Default,' 'Gnome,' 'Gnome Classic,' is selected and the login button is pressed. An unresponsive desktop background displays with no cursor.
The desktop appears to start normally only when 'Gnome on Wayland' is selected. (However, some applications still have display issues on Wayland, including Gedit. Therefore, this workaround is not very satisfactory.)
Commandline: /usr/bin/unattended-upgrade
Upgrade: libxcursor1:amd64 (1:1.1.14-1+b4, 1:1.1.14-1+deb9u1)
End-Date: 2017-12-09 00:11:57
Start-Date: 2017-12-10 19:54:15
Commandline: packagekit role='update-packages'
Upgrade: dbus-x11:amd64 (1.10.22-0+deb9u1, 1.10.24-0+deb9u1), libdbus-1-3:amd64 (1.10.22-0+deb9u1, 1.10.24-0+deb9u1), linux-libc-dev:amd64 (4.9.51-1, 4.9.65-3), fig2dev:amd64 (1:3.2.6a-2, 1:3.2.6a-2+deb9u1), transfig:amd64 (1:3.2.6a-2, 1:3.2.6a-2+deb9u1), dbus:amd64 (1.10.22-0+deb9u1, 1.10.24-0+deb9u1), python2.7-minimal:amd64 (2.7.13-2, 2.7.13-2+deb9u2), libsqlite3-0:amd64 (3.16.2-5, 3.16.2-5+deb9u1), libicu57:amd64 (57.1-6, 57.1-6+deb9u1), liblouis12:amd64 (3.0.0-3+b1, 3.0.0-3+deb9u1), linux-image-4.9.0-4-amd64:amd64 (4.9.51-1, 4.9.65-3), libpython2.7:amd64 (2.7.13-2, 2.7.13-2+deb9u2), python2.7:amd64 (2.7.13-2, 2.7.13-2+deb9u2), python3-louis:amd64 (3.0.0-3, 3.0.0-3+deb9u1), linux-headers-4.9.0-4-common:amd64 (4.9.51-1, 4.9.65-3), linux-compiler-gcc-6-x86:amd64 (4.9.51-1, 4.9.65-3), gdm3:amd64 (3.22.3-3, 3.22.3-3+deb9u1), gir1.2-gdm-1.0:amd64 (3.22.3-3, 3.22.3-3+deb9u1), libxkbcommon-x11-0:amd64 (0.7.1-1, 0.7.1-2~deb9u1), libgdm1:amd64 (3.22.3-3, 3.22.3-3+deb9u1), linux-kbuild-4.9
:amd64 (4.9.51-1, 4.9.65-3), iproute2:amd64 (4.9.0-1, 4.9.0-1+deb9u1), openssh-client:amd64 (1:7.4p1-10+deb9u1, 1:7.4p1-10+deb9u2), libpython2.7-minimal:amd64 (2.7.13-2, 2.7.13-2+deb9u2), liblouis-data:amd64 (3.0.0-3, 3.0.0-3+deb9u1), linux-headers-4.9.0-4-amd64:amd64 (4.9.51-1, 4.9.65-3), dbus-user-session:amd64 (1.10.22-0+deb9u1, 1.10.24-0+deb9u1), libpython2.7-stdlib:amd64 (2.7.13-2, 2.7.13-2+deb9u2), libxkbcommon0:amd64 (0.7.1-1, 0.7.1-2~deb9u1), base-files:amd64 (9.9+deb9u2, 9.9+deb9u3)
End-Date: 2017-12-10 19:56:04
~$ uname -r
4.9.0-4-amd64
~$ lsb_release -d
Description: Debian GNU/Linux 9.3 (stretch)
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 9.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Reply to: