GNOME Bugzilla – Bug 470600
crash in Panel: lkashf
Last modified: 2007-09-02 13:07:35 UTC
Version: 2.18.3 What were you doing when the application crashed? lkashf Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 38416384 vsize: 38416384 resident: 19492864 share: 16265216 rss: 19492864 rss_rlim: 4294967295 CPU usage: start_time: 1188193599 rtime: 66 utime: 57 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209071904 (LWP 2805)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 158111
Thread 1 (Thread -1209071904 (LWP 2805))
----------- .xsession-errors (21 sec old) --------------------- ** (gnome-panel:2805): WARNING **: panel-applet-frame.c:1349: failed to load applet OAFIID:GNOME_WindowListApplet (cannot get popup component): Unknown CORBA exception id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0' ** (gnome-panel:2805): WARNING **: panel-applet-frame.c:1349: failed to load applet OAFIID:GNOME_KeyboardApplet (cannot get popup component): Unknown CORBA exception id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0' (gnome-panel:2805): Bonobo-WARNING **: Cannot get value: Unknown CORBA exception id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0' (gnome-panel:2805): Bonobo-WARNING **: Cannot get value: Unknown CORBA exception id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0' ** ERROR **: file orbit-object.c: line 159 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0) aborting... --------------------------------------------------
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 452428 ***