gnome-panel crashed with SIGSEGV in ORBit_c_stub_invoke()

[Murali]

Binary package hint: gnome-panel

After the Desktop is loaded 2crashes occured

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-panel 1:2.30.2-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
Architecture: i386
Date: Mon Sep 13 06:21:18 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-panel
GConfNonDefault:
 /apps/panel/general/applet_id_list=[trashapplet_screen0,workspace_switcher_screen0,window_list_screen0,show_desktop_button_screen0,indicator_applet_screen0,notification_area_screen0,clock_screen0]
 /apps/panel/general/object_id_list=[browser_launcher_screen0,menu_bar_screen0,object_1]
 /apps/panel/general/toplevel_id_list=[bottom_panel_screen0,top_panel_screen0]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
ProcCmdline: gnome-panel
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xe621f3 <ORBit_c_stub_invoke+83>: mov 0xc(%edx),%eax
 PC (0x00e621f3) ok
 source "0xc(%edx)" (0x0000000b) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 ORBit_c_stub_invoke () from /usr/lib/libORBit-2.so.0
 Bonobo_Unknown_ref () from /usr/lib/libbonobo-activation.so.4
 bonobo_object_dup_ref () from /usr/lib/libbonobo-2.so.0
 bonobo_control_frame_bind_to_control () from /usr/lib/libbonoboui-2.so.0
 bonobo_widget_construct_control_from_objref () from /usr/lib/libbonoboui-2.so.0
Title: gnome-panel crashed with SIGSEGV in ORBit_c_stub_invoke()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[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 #207958, 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.