GNOME Bugzilla – Bug 467963
crash in File Browser: looking for built.xml fi...
Last modified: 2007-08-21 20:24:47 UTC
Version: 2.18.3 What were you doing when the application crashed? looking for built.xml file 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 87724032 vsize: 87724032 resident: 35475456 share: 21360640 rss: 35475456 rss_rlim: 4294967295 CPU usage: start_time: 1187443500 rtime: 4048 utime: 2691 stime: 1357 cutime:0 cstime: 2 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208486176 (LWP 2714)] [New Thread -1231946864 (LWP 3676)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 156149
Thread 2 (Thread -1231946864 (LWP 3676))
----------- .xsession-errors --------------------- May lead to memory leak and poor performance. Failed to load Main-Class manifest attribute from /root/jclic/jclic-0.1.2.2/author.jar Failed to load Main-Class manifest attribute from /root/jclic/jclic-0.1.2.2/author.jar GC Warning: Repeated allocation of very large block (appr. size 331776): May lead to memory leak and poor performance. GC Warning: Repeated allocation of very large block (appr. size 331776): May lead to memory leak and poor performance. --- Hash table keys for warning below: --> file:///root (nautilus:3662): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:2714): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x3715c)! --------------------------------------------------
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 454799 ***