mate-screenshot crashed with SIGSEGV in gdk_property_get()

[Paul Tansom]

Auto created report so not too much to add. I took the screenshot with the PrtSc key and all appeared to go well with the save. This error report appeared and I've checked that the screenshot is saved where I expected it to be and looks OK.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: mate-utils 1.18.2-1build1
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Sep 3 17:26:17 2017
ExecutablePath: /usr/bin/mate-screenshot
InstallationDate: Installed on 2017-06-16 (78 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: mate-screenshot -w
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f8469b2b940 <gdk_property_get>: mov 0x18(%rdi),%rax
 PC (0x7f8469b2b940) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mate-utils
StacktraceTop:
 gdk_property_get () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 screenshot_get_window_title ()
 ?? ()
 ?? ()
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: mate-screenshot crashed with SIGSEGV in gdk_property_get()
UpgradeStatus: Upgraded to artful on 2017-09-01 (1 days ago)
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 #1638835, 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.