wnck-applet crashed with SIGSEGV in g_closure_invoke()

[Majestyx]

Binary package hint: gnome-panel

anytime i want to go to the desktop switcher(applet) properties the applet crashes. after a new login in GOME the applet was back

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Feb 21 22:28:57 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gnome-panel/wnck-applet
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: gnome-panel 1:2.29.6-0ubuntu2
ProcCmdline: /usr/lib/gnome-panel/wnck-applet --oaf-activate-iid=OAFIID:GNOME_Wncklet_Factory --oaf-ior-fd=31
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SegvAnalysis:
 Segfault happened at: 0x804c6f6: mov (%ebx),%eax
 PC (0x0804c6f6) ok
 source "(%ebx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/libbonoboui-2.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 bonobo_closure_invoke_va_list ()
Title: wnck-applet crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.32-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1370): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (Do:1371): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.
 (gnome-power-manager:1368): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' 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 #508452, 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.