GNOME Bugzilla – Bug 464674
crash in Open Folder: I am searching for a fil...
Last modified: 2007-08-09 22:04:27 UTC
Version: 2.18.3 What were you doing when the application crashed? I am searching for a file,when i select the filesystem,it is very slow and crash. 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: Crux Icon Theme: Crux Memory status: size: 132521984 vsize: 132521984 resident: 39190528 share: 23851008 rss: 39190528 rss_rlim: 4294967295 CPU usage: start_time: 1186569462 rtime: 8966 utime: 7306 stime: 1660 cutime:0 cstime: 4 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 -1208264992 (LWP 4117)] [New Thread -1220854896 (LWP 6874)] [New Thread -1254098032 (LWP 6115)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 153700
Thread 2 (Thread -1220854896 (LWP 6874))
----------- .xsession-errors (23 sec old) --------------------- 20:12:03 : GUI Setup Completed 20:12:03 : Setup Yum : Transaction Set 20:12:03 : Setup Yum : RPM Db. 20:12:03 : Setup Yum : Repositories. Loading mirror speeds from cached hostfile 20:12:06 : Setup Yum : Package Sacks 0 packages excluded due to repository protections 0 packages excluded due to repository priority protections 20:12:15 : Setup Yum : Updates 20:12:25 : Setup Yum : Groups Loading mirror speeds from cached hostfile 20:12:26 : Setup Yum : Base setup completed 20:12:26 : Building Package Lists (nautilus:4117): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed --------------------------------------------------
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 ***