lxpanel crashed with SIGSEGV in g_closure_invoke()

[Lyn Perrine]

Lxpanel crashed when I was using gparted and then finished with partitioning my usb stick.
lxpanel:
  Installed: 0.8.1-1ubuntu1
  Candidate: 0.8.1-1ubuntu1
  Version table:
 *** 0.8.1-1ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
        100 /var/lib/dpkg/status
Description: Ubuntu Wily Werewolf (development branch)
Release: 15.10

I expected lxpanel to not crash instead it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: lxpanel 0.8.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0
Uname: Linux 4.2.0-10-generic x86_64
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
Config_Home_Lubuntu:
 [Command]
 Logout=lxsession-default quit
CrashCounter: 1
CurrentDesktop: LXDE
Date: Fri Sep 18 11:12:36 2015
ExecutablePath: /usr/bin/lxpanel
InstallationDate: Installed on 2014-09-30 (352 days ago)
InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140930)
JournalErrors:
 No journal files were found.
 -- No entries --
ProcCmdline: lxpanel --profile Lubuntu
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x563452758e06: mov (%r15),%rdi
 PC (0x563452758e06) ok
 source "(%r15)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: lxpanel
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: lxpanel crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to wily on 2015-08-07 (41 days ago)
UserGroups: fuse libvirtd 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 #1279367, 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.