xfce4-color-settings crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

[Luzius Thöny]

Installed the latest eoan upgrades (Xfce 4.14 packages), opened the color-settings dialogue and soon after this error popped up.

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: xfce4-settings 4.14.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
Uname: Linux 5.2.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Aug 15 15:08:18 2019
ExecutablePath: /usr/bin/xfce4-color-settings
InstallationDate: Installed on 2019-06-30 (45 days ago)
InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190630)
ProcCmdline: xfce4-color-settings --socket-id=62916069
SegvAnalysis:
 Segfault happened at: 0x7fc695efc931 <g_type_check_instance_is_fundamentally_a+17>: mov (%rax),%rax
 PC (0x7fc695efc931) ok
 source "(%rax)" (0x10102c09e60080) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: xfce4-settings
StacktraceTop:
 g_type_check_instance_is_fundamentally_a () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: xfce4-color-settings crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

[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 #1835579, 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.