mate-panel crashed with SIGSEGV in g_slist_remove_all()

[oldrocker99]

On startup, right after an Xorg crash. No problem seen with the MATE panels at all.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: mate-panel 1.10.1+gfdl1-1
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: MATE
Date: Mon Oct 12 18:06:05 2015
ExecutablePath: /usr/bin/mate-panel
InstallationDate: Installed on 2015-10-09 (3 days ago)
InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
ProcCmdline: mate-panel
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f86716fc9ac <g_slist_remove_all+44>: cmp %rbp,(%rdi)
 PC (0x7f86716fc9ac) ok
 source "%rbp" ok
 destination "(%rdi)" (0x6172672d73006c65) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: mate-panel
StacktraceTop:
 g_slist_remove_all () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 gtk_rc_reset_styles () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
Title: mate-panel crashed with SIGSEGV in g_slist_remove_all()
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 #1425341, 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.