gnome-panel crashed with SIGSEGV in g_type_check_instance_cast()

[Matthias Andree]

multiple file operations in progress at the same time, or quitting gimp, caused this

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-panel 1:3.8.0-1ubuntu12.2
ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
Uname: Linux 3.13.0-49-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.9
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Thu Apr 16 01:44:14 2015
ExecutablePath: /usr/bin/gnome-panel
GsettingsChanges: b'org.gnome.gnome-panel.run-dialog' b'history' b'[\'gnome-panel --replace\', \'gnome-panel\', \'geeqie "..., \'clementine\', \'xterm -fa MiscFixed -fs 10 -fg lightgreen -bg black\', \'xterm\', \'VirtualBox\', \'gnome-calculator\', \'nautilus\', \'VirtualBox\', \'gnome-calculator\', \'VirtualBox\', \'gnome-calculator\']'
ProcCmdline: gnome-panel --replace
SegvAnalysis:
 Segfault happened at: 0x7fdddd06134c <g_type_check_instance_cast+28>: mov (%rax),%rdi
 PC (0x7fdddd06134c) ok
 source "(%rax)" (0x1c00000d00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 g_type_check_instance_cast (type_instance=0x1408040, iface_type=21529888) at /build/buildd/glib2.0-2.40.2/./gobject/gtype.c:4002
 ?? () from /usr/lib/libpanel-applet-4.so.0
 call_in_idle_cb (user_data=0x7fddcc003120) at /build/buildd/glib2.0-2.40.2/./gio/gdbusconnection.c:4875
 g_main_dispatch (context=0x11a41e0) at /build/buildd/glib2.0-2.40.2/./glib/gmain.c:3064
 g_main_context_dispatch (context=context@entry=0x11a41e0) at /build/buildd/glib2.0-2.40.2/./glib/gmain.c:3663
Title: gnome-panel crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: Upgraded to trusty on 2014-08-29 (229 days ago)
UserGroups: adm admin audio cdrom dialout dip disk fax floppy fuse libvirtd lpadmin netdev plugdev pulse sambashare saned tape vboxusers video

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