GNOME Bugzilla – Bug 472687
crash in File Browser:
Last modified: 2007-09-04 16:27:57 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.20-2925.13.fc7xen #1 SMP Tue Jul 17 10:38:27 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 128159744 vsize: 128159744 resident: 39714816 share: 35414016 rss: 39714816 rss_rlim: 4294967295 CPU usage: start_time: 1188600149 rtime: 52 utime: 44 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208297760 (LWP 3695)] (no debugging symbols found) 0x0049c402 in __kernel_vsyscall ()
+ Trace 159720
Thread 1 (Thread -1208297760 (LWP 3695))
----------- .xsession-errors (11 sec old) --------------------- Loading "installonlyn" plugin ** ERROR **: file orbit-object.c: line 159 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0) aborting... Initializing nautilus-flac-converter extension Initializing nautilus-image-converter extension seahorse nautilus module initialized Initializing nautilus-open-terminal extension Initializing nautilus-search-tool extension Initializing nautilus-flac-converter extension Initializing nautilus-image-converter extension seahorse nautilus module initialized Initializing nautilus-open-terminal extension Initializing nautilus-search-tool extension TIMING timeout (HTTP Connection Pool Cleanup) too slow (1.598 secs) --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 471979 ***