GNOME Bugzilla – Bug 470319
crash in Panel:
Last modified: 2007-09-02 13:07:11 UTC
Version: 2.18.3 What were you doing when the application crashed? 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 40898560 vsize: 40898560 resident: 23494656 share: 14422016 rss: 23494656 rss_rlim: 4294967295 CPU usage: start_time: 1188087164 rtime: 24 utime: 17 stime: 7 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 -1208617248 (LWP 3216)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 157919
Thread 1 (Thread -1208617248 (LWP 3216))
----------- .xsession-errors --------------------- Tracker version 0.6.0 Copyright (c) 2005-2006 by Jamie McCracken (jamiemcc@gnome.org) This program is free software and comes without any warranty. It is licensed under version 2 or later of the General Public License which can be viewed at http://www.gnu.org/licenses/gpl.txt Initialising tracker... throttle level is 0 Initializing nautilus-flac-converter extension Initializing nautilus-image-converter extension seahorse nautilus module initialized Initializing nautilus-search-tool extension Initializing nautilus-open-terminal extension ** 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 ***