gnome-screenshot crashed with signal 5

[W9DKI]

Ubuntu screencapture on 18.04-beta crashed unexpectedly, but the screen capture shift+PrtScn did work and produce the highlighted area_box.png

Not really sure why the system reported an unexpected closure. I was somewhat surprised but the error/warning box popped up just after the screen capture.png appeared in the pictures directory as it should..with no apparent artifacts or problems.

This appears to be like a relatively "minor"issue to me?
Sorry I am running a Cinnamon desktop not gnome as I should..in xorg, X-11 not Wayland and I am using most current Nvidia drivers on a Titan / dual monitor DVI system rather than HDMI because of the dual monitor default choice problem with GDM/gnome/wayland

Don / w9dki
Hilbert Space Technical Arts
w: www.hspacetech.com
e: <email address hidden>

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-screenshot 3.25.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Fri Jan 12 04:34:46 2018
ExecutablePath: /usr/bin/gnome-screenshot
InstallationDate: Installed on 2017-12-22 (21 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
ProcCmdline: gnome-screenshot --area
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-screenshot
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 XInternAtom () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 gdk_x11_atom_to_xatom_for_display () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-screenshot crashed with signal 5
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 #1725383, 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.