Error message after booting

[John S]

Binary package hint: gnome-panel

Ubuntu 9.10

Was doing normal system boot. Expected result: Normal startup without errors. What happened: Error message appeared after logging on.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Nov 6 17:49:46 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-panel
Package: gnome-panel 1:2.28.0-0ubuntu6
ProcCmdline: gnome-panel
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x5f4694 <ORBit_c_stub_invoke+100>: mov 0xc(%esi),%eax
 PC (0x005f4694) ok
 source "0xc(%esi)" (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()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:1805): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1805): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:1901): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1893): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (gnome-panel:1892): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -4 and height 24

[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.