GDM3 fails to login following PureOS upgrade

Upon successfully upgrading PureOS 8.0 distribution based on linux-image-4.12 to linux-image-4.14, 700+ packages have been installed or upgraded from the Purism repository as of 2018.01.20 that is Jan 20, 2018:

% tail /etc/apt/sources.list
deb green main

% sudo apt update
% sudo apt upgrade

% sudo apt full-upgrade
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

GDM3 service has also been upgraded from version 3.24 to 3.26 which exhibits regressive behaviour. Starting at the GDM3 login screen, upon selecting the account, filling the corresponding password, and hitting the “Sign In” button with “GNOME” option, there is a short visual distortion of the screen and the login screen appears again without any error message.

Logging into a virtual terminal such as /dev/tty3, reveals a newly generated core file along with a recently modified authentication file:

% echo ${UID}

% file ~/core
~/core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, \
from '/usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 -listen 5 -displayfd', \
real uid: 1000, effective uid: 1000, real gid: 1000, effective gid: 1000, \
execfn: '/usr/bin/Xwayland', platform: 'x86_64'

% file ~/.ICEauthority
~/.ICEauthority: data

The same GDM3 service instance remains active at all times:

% dpkg -l gdm3 | tail -1
ii  gdm3  amd64  GNOME Display Manager

% systemctl status gdm3
* gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service: statis: vendor preset: enabled)
   Active: active (running) since Sun 2018-01-21 ...; 30min ago
  Process: 887 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS)
 Main PID: 898 (gdm3)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/gdm.service
           `-898 /usr/sbin/gdm3

Has anyone else experienced this regression, and knows how to fix it?

The repository is; if you change your /etc/apt/sources.list file to reflect this, you should be able to update without any more problems.

Upon retry and failure to login with GDM3, a related error is being reported to system log:

% sudo tail -8 /var/log/messages
gnome-shell[3062]: JS ERROR: TypeError: formattedTime is null#012formatTime@resource:///org/gnome/shell/misc/util.js:286:5#012WorldClocksSection<.updateLabels@resource:///org/gnome/shell/ui/dateMenu.js:196:28#012wrapper@resource:///...@resource:///org/gnome/shell/ui/main.js:126:5#012@<main>:1:31
gnome-shell[3062]: Execution of main.js threw exception: JS_EvaluateScript() failed
org.gnome.Shell.desktop[3062]: (EE)
org.gnome.Shell.desktop[3062]: Fatal server error:
org.gnome.Shell.desktop[3062]: (EE) failed to read Wayland events: Connection reset by peer
org.gnome.Shell.desktop[3062]: (EE)
gnome-session[3033]: gnome-session-binary[3033]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
gdm3: GdmDisplay: display lasted 1.458587 seconds