Bug#881893: xwayland: FatalError() when I open the closed Laptop Lid in accident (not always triggered)

[toby cabot <toby.cabot@affectiva.com>]

Package: xwayland
Version: 2:1.19.5-1
Followup-For: Bug #881893

Dear Maintainer,

I see the same crash on a desktop machine when I activate the screen
lock, or when I log back in from the screen lock, not sure which.  The
screen locks fine and appears to log in fine but all of the apps that
I ran are gone and there's a core file in my home directory.

It doesn't happen if I lock the screen and log back in very quickly
but if I wait for a few minutes then it does happen.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.0-1-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)

Versions of packages xwayland depends on:
ii  libaudit1           1:2.8.1-2
ii  libbsd0             0.8.6-3
ii  libc6               2.25-3
ii  libdrm2             2.4.88-1
ii  libegl1             1.0.0-1
ii  libepoxy0           1.4.3-1
ii  libgbm1             17.2.5-1
ii  libgcrypt20         1.8.1-4
ii  libgl1              1.0.0-1
ii  libpixman-1-0       0.34.0-1
ii  libselinux1         2.7-2
ii  libsystemd0         235-3
ii  libwayland-client0  1.14.0-1+b1
ii  libxau6             1:1.0.8-1+b2
ii  libxdmcp6           1:1.1.2-3
ii  libxfont2           1:2.0.1-4
ii  libxshmfence1       1.2-1+b2
ii  xserver-common      2:1.19.5-1

xwayland recommends no packages.

xwayland suggests no packages.

-- no debconf information