gnome-panel causes Segmentation fault in 11.10 gnome classic

[keepitsimpleengr]

In release upgrade from 11.04, panels do not appear when logging on with Gnome Classic. Opening a terminal and attempting to start gnamoe panel results in:
....$ gnome-panel

** (gnome-panel:8705): CRITICAL **: unable to create '/media/spare/var/cache/cache-10.4/dconf'; dconf will not work properly.

** (gnome-panel:8705): CRITICAL **: unable to create '/media/spare/var/cache/cache-10.4/dconf'; dconf will not work properly.

(gnome-panel:8705): Gtk-CRITICAL **: gtk_style_context_get: assertion `priv->widget_path != NULL' failed
Segmentation fault

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-panel 1:3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-19.33-generic 3.0.27
Uname: Linux 3.0.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Sat May 19 09:55:39 2012
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-panel
UpgradeStatus: Upgraded to oneiric on 2012-05-19 (0 days ago)

[penalvch (penalvch)]

keepitsimpleengr, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get -y install gnome-panel-dbg && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
gksudo gedit /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs