gnome-panel crashed with SIGSEGV in ORBit_c_stub_invoke()

[Shirish Nigam]

Binary package hint: gnome-panel

After installing new codecs in Totem player i was watching video suddenly sound became sluggish and video too. then i thought i might need to restart the system so after restart i got this error which i'm reporting here.

btw i'm running ubuntu 10.4 in virtual box 3.1.6 r593398 as a guest and my host O.S windows 7 64-bit.

Just upgraded from Ubuntu 9.10 to 10.4 last night.

Note : I'm ubuntu newbie so i'm not sure how to find the source of the bug.

Thanks

Shirish

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-panel 1:2.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Sun Apr 18 18:02:02 2010
ExecutablePath: /usr/bin/gnome-panel
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: gnome-panel
ProcEnviron:
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x13f1f3 <ORBit_c_stub_invoke+83>: mov 0xc(%edx),%eax
 PC (0x0013f1f3) 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 ()
 bonobo_object_dup_ref () from /usr/lib/libbonobo-2.so.0
 bonobo_control_frame_bind_to_control ()
 bonobo_widget_construct_control_from_objref ()
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.