vino-server crashed with SIGSEGV in _XSend()

[Trip98]

Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
vino:
  Installed: 3.22.0-2ubuntu1
  Candidate: 3.22.0-2ubuntu1

after logging in on Xorg then logging back in under wayland this error pops up. on login.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: vino 3.22.0-2ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.8-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec 30 09:40:37 2017
ExecutablePath: /usr/lib/vino/vino-server
InstallationDate: Installed on 2017-12-29 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
ProcCmdline: /usr/lib/vino/vino-server
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f5af22bc3ce <_XSend+126>: mov (%rax),%rdx
 PC (0x7f5af22bc3ce) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: vino
StacktraceTop:
 _XSend () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XQueryExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libXtst.so.6
 XTestQueryExtension () from /usr/lib/x86_64-linux-gnu/libXtst.so.6
 ?? ()
Title: vino-server crashed with SIGSEGV in _XSend()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1724572, so 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. Please continue to report any other bugs you may find.