unity-2d-panel crashed with SIGSEGV in QList<AbstractX11EventFilter*>::removeAll()

[Xristh]

Binary package hint: unity-2d

change session from unity-2d to gnome classic and themes return to gnome default (no ubuntu default theme, instead is the gnome default theme) and the message apeared

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity-2d-panel 3.2.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
Uname: Linux 2.6.38-1-generic i686
Architecture: i386
Date: Fri Feb 4 15:07:05 2011
ExecutablePath: /usr/bin/unity-2d-panel
ProcCmdline: unity-2d-panel
ProcEnviron:
 LANGUAGE=es_CL:es:en_GB:en
 LANG=es_CL.UTF-8
 LC_MESSAGES=es_CL.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x3a6a77 <_ZN5QListIP22AbstractX11EventFilterE9removeAllERKS1_+23>: mov (%edx),%eax
 PC (0x003a6a77) ok
 source "(%edx)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
 QList<AbstractX11EventFilter*>::removeAll(AbstractX11EventFilter* const&) () from /usr/lib/libuqpanel.so.0
 Unity2dApplication::removeX11EventFilter(AbstractX11EventFilter*) () from /usr/lib/libuqpanel.so.0
 AbstractX11EventFilter::~AbstractX11EventFilter() () from /usr/lib/libuqpanel.so.0
 KeyboardModifiersMonitor::~KeyboardModifiersMonitor() () from /usr/lib/libuqpanel.so.0
 KeyboardModifiersMonitor::~KeyboardModifiersMonitor() () from /usr/lib/libuqpanel.so.0
Title: unity-2d-panel crashed with SIGSEGV in QList<AbstractX11EventFilter*>::removeAll()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
XsessionErrors: (nautilus:4913): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

[Apport retracing service (apport)]

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 #708429, 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.