GNOME Bugzilla – Bug 489115
crash in Panel: tjbkfljfkjr sfnqjkg ajgo...
Last modified: 2007-10-28 15:20:45 UTC
Version: 2.18.3 What were you doing when the application crashed? tjbkfljfkjr sfnqjkg ajgojkv 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.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 299773952 vsize: 299773952 resident: 22122496 share: 17481728 rss: 22122496 rss_rlim: 18446744073709551615 CPU usage: start_time: 1193077968 rtime: 21 utime: 17 stime: 4 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496355760 (LWP 25994)] (no debugging symbols found) 0x00000038d6a0d945 in waitpid () from /lib64/libpthread.so.0
+ Trace 172020
Thread 1 (Thread 46912496355760 (LWP 25994))
----------- .xsession-errors --------------------- localuser:anartia being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/25875 Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-calc.desktop for panel launcher: No such file or directory Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. ** 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 ***