budgie-daemon crashed with SIGSEGV in g_object_unref()

[Rajat Goyal]

I'm not sure what to fill here. I experienced this while running 'artful' in VirtualBox.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: budgie-core 10.3.1-4
ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
Uname: Linux 4.11.0-13-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Budgie:GNOME
Date: Thu Aug 10 22:07:01 2017
ExecutablePath: /usr/bin/budgie-daemon
InstallationDate: Installed on 2017-08-05 (5 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 (20170725.1)
ProcCmdline: budgie-daemon
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_IN
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f159576b271: movq $0x0,(%rax,%rdx,8)
 PC (0x7f159576b271) ok
 source "$0x0" ok
 destination "(%rax,%rdx,8)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: budgie-desktop
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libwnck-3.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? ()
 __libc_start_main (main=0x48dfcec820, argc=1, argv=0x7ffd019d0078, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd019d0068) at ../csu/libc-start.c:291
Title: budgie-daemon crashed with SIGSEGV in g_object_unref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker 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 #1704668, 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.