budgie-polkit-dialog crashed with SIGSEGV in g_datalist_id_set_data_full()

[seirra saffron francis diamond blake]

unknown

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: budgie-core 10.4-1ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Budgie:GNOME
Date: Fri Oct 20 11:46:49 2017
ExecutablePath: /usr/bin/budgie-polkit-dialog
InstallationDate: Installed on 2017-10-20 (0 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
ProcCmdline: budgie-polkit-dialog
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: 0x7f55bcffe6e6 <g_datalist_id_set_data_full+470>: movdqu (%rdx),%xmm0
 PC (0x7f55bcffe6e6) ok
 source "(%rdx)" (0x5639b320c310) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: budgie-desktop
StacktraceTop:
 g_datalist_id_set_data_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 __libc_start_main (main=0x562a5141a960, argc=1, argv=0x7ffff9653178, init=<optimised out>, fini=<optimised out>, rtld_fini=<optimised out>, stack_end=0x7ffff9653168) at ../csu/libc-start.c:308
 ?? ()
Title: budgie-polkit-dialog crashed with SIGSEGV in g_datalist_id_set_data_full()
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 #1712120, 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.