gnome-panel crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv()

[penalvch]

What is expected to happen is when one holds Super+Alt > secondary click an empty space of the gnome-panel > click Add to Panel... > Clock > Add > Close > hold Super+Alt > secondary click the newly added Clock > Remove from Panel gnome-panel doesn't crash.

What happens instead is it does. This would appear innocuous as it isn't repeatable so far, and didn't have any noticeable, negative effect on the existing panel.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-panel 1:3.8.0-1ubuntu12.1
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Aug 24 03:24:26 2014
ExecutablePath: /usr/bin/gnome-panel
GsettingsChanges: b'org.gnome.gnome-panel.run-dialog' b'history' b"['sudo reboot', 'sudo nautilus', 'nautilus']"
InstallationDate: Installed on 2014-06-21 (63 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: gnome-panel
SegvAnalysis:
 Segfault happened at: 0x7f25e796815d: mov (%rbx),%rbp
 PC (0x7f25e796815d) ok
 source "(%rbx)" (0x7f2500000020) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 ?? () from /usr/lib/gnome-panel/4.0/libclock-applet.so
 g_cclosure_marshal_VOID__STRINGv () 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
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-panel crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv()
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 #1358063, 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.