GNOME Bugzilla – Bug 528442
crash in Panel: lauching gnome panel aft...
Last modified: 2008-04-16 17:27:46 UTC
Version: 2.22.1.2 What were you doing when the application crashed? lauching gnome panel after logging Distribution: Gentoo Base System release 2.0.0 Gnome Release: 2.22.1 2008-04-10 (Gentoo) BugBuddy Version: 2.22.0 System: Linux 2.6.25-rc9 #3 SMP PREEMPT Mon Apr 14 18:33:11 CEST 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Unity Icon Theme: Gion Memory status: size: 336867328 vsize: 336867328 resident: 20869120 share: 15355904 rss: 20869120 rss_rlim: 18446744073709551615 CPU usage: start_time: 1208365135 rtime: 70 utime: 57 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) 0x000000325060e3a5 in waitpid () from /lib/libpthread.so.0
+ Trace 195393
----------- .xsession-errors --------------------- Could not find the frame base for "giop_connection_handle_input". Could not find the frame base for "link_connection_io_handler". Could not find the frame base for "link_source_dispatch". Could not find the frame base for "link_main_iteration". Could not find the frame base for "giop_recv_buffer_get". Could not find the frame base for "ORBit_small_invoke_stub". Could not find the frame base for "ORBit_small_invoke_stub_n". Could not find the frame base for "ORBit_c_stub_invoke". Could not find the frame base for "ORBit_c_stub_invoke". Could not find the frame base for "async_recv_cb". Could not find the frame base for "giop_invoke_async". Could not find the frame base for "handle_reply". Could not find the frame base for "giop_connection_handle_input". Could not find the frame base for "link_connection_io_handler". Could not find the frame base for "link_source_dispatch". --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 527441 ***