gnome-panel crashed with SIGSEGV in gtk_container_forall()

[marcobra (Marco Braida)]

Description: Ubuntu quantal (development branch)
Release: 12.10

gnome-panel:
  Installato: 1:3.5.4-0ubuntu2
  Candidato: 1:3.5.4-0ubuntu2
  Tabella versione:
 *** 1:3.5.4-0ubuntu2 0
        500 http://archive.ubuntu.com/ubuntu/ quantal/universe i386 Packages
        100 /var/lib/dpkg/status

I get this crash on a just upgraded 12.04 to 12.10 desktop pc

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-panel 1:3.5.4-0ubuntu2 [modified: usr/bin/gnome-desktop-item-edit usr/bin/gnome-panel usr/bin/panel-test-applets]
ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
Uname: Linux 3.5.0-10-generic i686
ApportVersion: 2.4-0ubuntu6
Architecture: i386
CrashCounter: 1
Date: Wed Aug 15 17:06:40 2012
ExecutablePath: /usr/bin/gnome-panel
ExecutableTimestamp: 1343300326
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
ProcCmdline: gnome-panel
ProcCwd: /home/simonetta
SegvAnalysis:
 Segfault happened at: 0x4e07124f: mov 0x50(%eax),%edx
 PC (0x4e07124f) ok
 source "0x50(%eax)" (0xaaaaaafa) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 gtk_container_forall () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
Title: gnome-panel crashed with SIGSEGV in gtk_container_forall()
UpgradeStatus: Upgraded to quantal on 2012-08-15 (0 days ago)
UserGroups: adm admin audio cdrom debian-tor dialout dip fax floppy fuse icecast lpadmin netdev plugdev powerdev sambashare tape vboxusers video
mtime.conffile..etc.xdg.autostart.indicator.applet.desktop: 2012-04-28T05:18:08.290891

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