GNOME Bugzilla – Bug 521770
crash in Home Folder: Hi, I'm start one search...
Last modified: 2008-03-11 18:24:10 UTC
What were you doing when the application crashed? Hi, I'm start one search in FIle System only. Thank's Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 97972224 vsize: 97972224 resident: 35057664 share: 20623360 rss: 35057664 rss_rlim: 4294967295 CPU usage: start_time: 1205240514 rtime: 3308 utime: 3006 stime: 302 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 -1208449312 (LWP 8561)] [New Thread -1277867120 (LWP 9338)] [New Thread -1232110704 (LWP 9303)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 192075
Thread 2 (Thread -1277867120 (LWP 9338))
----------- .xsession-errors --------------------- package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. ** (gnome-system-monitor:8937): WARNING **: SELinux was found but is not enabled. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. ** (gnome-system-monitor:9239): WARNING **: SELinux was found but is not enabled. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. (nautilus:8561): 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 ***