Binary package hint: gnome-panel
Just open in gnome safe session. and when any time execute gnome-panel --replace from console I get the same crash
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-panel 1:3.0.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.0-1.2-generic 3.0.0-rc3
Uname: Linux 3.0-1-generic i686
Architecture: i386
CrashCounter: 1
Date: Fri Jun 17 19:55:02 2011
ExecutablePath: /usr/bin/gnome-panel
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
ProcCmdline: gnome-panel
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
LANG=es_CL.utf8
LC_MESSAGES=en_US.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x57939f <gtk_widget_pop_verify_invariants+31>: mov 0x4c(%eax),%edx
PC (0x0057939f) ok
source "0x4c(%eax)" (0xaaaaaaf6) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
gtk_widget_pop_verify_invariants (widget=0x8f07000) at /build/buildd/gtk+3.0-3.1.6/./gtk/gtkwidget.c:8940
gtk_bin_forall (container=0x8f06808, include_internals=1, callback=0x580ee0 <gtk_widget_unrealize>, callback_data=0x0) at /build/buildd/gtk+3.0-3.1.6/./gtk/gtkbin.c:172
gtk_container_forall (container=0x8f06808, callback=0x580ee0 <gtk_widget_unrealize>, callback_data=0x0) at /build/buildd/gtk+3.0-3.1.6/./gtk/gtkcontainer.c:2030
gtk_widget_real_unrealize (widget=0x8f06808) at /build/buildd/gtk+3.0-3.1.6/./gtk/gtkwidget.c:10759
gtk_event_box_unrealize (widget=0x8f06808) at /build/buildd/gtk+3.0-3.1.6/./gtk/gtkeventbox.c:472
Title: gnome-panel crashed with SIGSEGV in gtk_widget_pop_verify_invariants()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #798141, 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.