gnome-panel crashed with SIGSEGV in panel_applet_lockable()

[Sesise]

Binary package hint: gnome-panel

Loading gnome-shell at start-up, not all applets loaded.

Evolution calendar events applet does not load correctly.

Cheers

ProblemType: Crash
Architecture: amd64
Date: Sun Mar 21 22:56:56 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gnome-panel
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
Package: gnome-panel 1:2.29.92.1-0ubuntu3
ProcCmdline: gnome-panel
ProcEnviron:
 LANG=es_ES.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
 Segfault happened at: 0x4347ea <panel_applet_lockable+58>: cmpl $0x3,0x0(%rbp)
 PC (0x004347ea) ok
 source "$0x3" ok
 destination "0x0(%rbp)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 panel_applet_lockable ()
 panel_applet_frame_sync_menu_state ()
 ?? ()
 ?? () from /usr/lib/libbonobo-activation.so.4
 ?? () from /usr/lib/libORBit-2.so.0
Title: gnome-panel crashed with SIGSEGV in panel_applet_lockable()
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1345): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (bluetooth-applet:1349): Gtk-CRITICAL **: gtk_action_set_sensitive: assertion `GTK_IS_ACTION (action)' failed
 (gnome-panel:1346): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion `global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' 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 #540873, 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.