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

[John McCaul]

I'm not sure if this is a duplicate as the bug report was initiated by apport without any effect in user-space

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: budgie-core 10.4+git20171031.10.g9f71bb8-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic i686
ApportVersion: 2.20.8-0ubuntu6
Architecture: i386
CrashCounter: 1
CurrentDesktop: Budgie:GNOME
Date: Sun Jan 21 16:00:33 2018
ExecutablePath: /usr/bin/budgie-polkit-dialog
InstallationDate: Installed on 2018-01-17 (4 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha i386 (20180115)
ProcCmdline: budgie-polkit-dialog
SegvAnalysis:
 Segfault happened at: 0xb71c2390 <g_datalist_id_set_data_full+400>: mov (%edx),%esi
 PC (0xb71c2390) ok
 source "(%edx)" (0x1943da5c) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: budgie-desktop
StacktraceTop:
 g_datalist_id_set_data_full () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? ()
 __libc_start_main (main=0x47a390, argc=1, argv=0xbfd33484, init=0x47efa0, fini=0x47f000, rtld_fini=0xb7f3be50 <_dl_fini>, stack_end=0xbfd3347c) 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
mtime.conffile..etc.xdg.autostart.budgie-desktop-nm-applet.desktop: 2018-01-17T18:59:19.184736
mtime.conffile..etc.xdg.autostart.budgie-desktop-screensaver.desktop: 2018-01-17T18:59:19.184736

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