gnome-panel crashed with SIGSEGV in g_signal_emit_valist()

[Peter Hultqvist]

After upgrading from 12.04 to 12.10 using "update-manager -d" with no errors on the way.

After logging in to a Ubuntu session I get my wallpaper and I can move the mouse but no other elements.

The crash happen when I go to the terminal(Ctrl+Alt+F1) and run "DISPLAY=:0.0 xterm", xterm starts but at the same time the crash report starts working.

I have run apt-get update; apt-get upgrade with successful result.

My hardware graphics card is an ATI Radeon HD 6000, which I used the vendors drivers for before.
After the upgrade I have both tried using them(which got an error, a different issue) and with them uninstalled.

I can run the Gnome session where I'm given the old 2D version.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-panel 1:3.5.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
Date: Mon Sep 3 22:24:43 2012
ExecutablePath: /usr/bin/gnome-panel
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120327.1)
ProcCmdline: gnome-panel
SegvAnalysis:
 Segfault happened at: 0x7f60fda85a45: mov 0x80(%rax),%edx
 PC (0x7f60fda85a45) ok
 source "0x80(%rax)" (0xaaaaaaaaaaaaab2a) 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/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.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_signal_emit_valist()
UpgradeStatus: Upgraded to quantal on 2012-09-02 (0 days ago)
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 #948667, 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.