Comment 34 for bug 1753776

Doing some testing:

- first modifying options into /etc/gdm3/custom.conf
  **** set [daemon] WaylandEnable=false to force xorg login :
 my feeling is that should be the default now as ubuntu as made that choice for the release (and wayland / apps still does not well together in many cases)

- then rebboting

And now the problem existing with my hardware and reported here is gone: no distorted screen.
That system is using the 'proposed' archive and is fully updated.
What is also different now: the login options (gear button) have dropped the wayland ones.

So my conclusion are:
- /etc/gdm3/custom.conf should use xorg, not wayland
- the issue reported gere seems have been introduced by the wayland (1.14.0-2) changes (patch)

*****
wayland (1.14.0-2) unstable; urgency=medium

  * debian/patches/CVE-2017-16612.patch: (Closes: #889681)
    - libXcursor before 1.1.15 has various integer overflows that could lead
      to heap buffer overflows when processing malicious cursors, e.g., with
      programs like GIMP. It is also possible that an attack vector exists
      against the related code in cursor/xcursor.c in Wayland through
      1.14.0.
  * switch back to use upstream tarball
  * debian/control: bump standards version, drop priority stanzas

 -- Héctor Orón Martínez <email address hidden> Sun, 04 Mar 2018 11:56:31 +0100
*******