xfce4-display-settings crashed when running in VirtualBox on Windows 10

[Ron Bentley]

I was running in Xubuntu 18.04 in VirtualBox on Windows 10. I went full screen with the viewer and then tried to adjust the desktop size to match the monitor resolution. As soon as I tried to open display settings, it crashed. (Bug submitted only because I was prompted to do that. I wouldn't necessarily classify this as high priority.)

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: xfce4-settings 4.12.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Apr 16 15:23:21 2018
ExecutablePath: /usr/bin/xfce4-display-settings
InstallationDate: Installed on 2018-03-07 (40 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
ProcCmdline: xfce4-display-settings
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x564cb2e10f14: movsd 0x10(%r13),%xmm0
 PC (0x564cb2e10f14) ok
 source "0x10(%r13)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xfce4-settings
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: xfce4-display-settings crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt 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 #1628250, 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.