mate-maximus crashed with signal 5 in _XReply()

[Jimmy Frydkær Jensen]

Not sure when this crash happened

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: mate-netbook 1.14.0-1
ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
Uname: Linux 4.4.0-25-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
CurrentDesktop: MATE
Date: Fri Jun 17 22:17:05 2016
ExecutablePath: /usr/bin/mate-maximus
InstallationDate: Installed on 2016-06-17 (0 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20160617)
ProcCmdline: mate-maximus
ProcEnviron:
 LANGUAGE=da
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=da_DK.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: mate-netbook
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? ()
 g_cclosure_marshal_VOID__OBJECTv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: mate-maximus crashed with signal 5 in _XReply()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 XGetWindowProperty (dpy=0x555ced3fc350, w=69206019, property=388, offset=0, length=5, delete=0, req_type=0, actual_type=0x7ffd87b4fd40, actual_format=0x7ffd87b4fd34, nitems=0x7ffd87b4fd48, bytesafter=0x7ffd87b4fd50, prop=0x7ffd87b4fd38) at ../../src/GetProp.c:69
 on_window_opened ()
 g_cclosure_marshal_VOID__OBJECTv () from /tmp/apport_sandbox_HFsRIC/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 _g_closure_invoke_va () from /tmp/apport_sandbox_HFsRIC/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /tmp/apport_sandbox_HFsRIC/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.