GNOME Bugzilla – Bug 483535
crash in Home Folder: Searching file.
Last modified: 2007-10-05 14:30:35 UTC
What were you doing when the application crashed? Searching 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.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: No Accessibility: Disabled GTK+ Theme: ThinIce Icon Theme: Vista-Inspirate_1.0 Memory status: size: 94781440 vsize: 94781440 resident: 42283008 share: 21250048 rss: 42283008 rss_rlim: 4294967295 CPU usage: start_time: 1191541980 rtime: 1104 utime: 1015 stime: 89 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208535328 (LWP 4360)] [New Thread -1284646000 (LWP 6186)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 167839
Thread 2 (Thread -1284646000 (LWP 6186))
----------- .xsession-errors --------------------- Unable to connect to yum-updatesd. Please ensure that the yum-updatesd 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. --- Hash table keys for warning below: --> file:///home/nelmar --> file:///home/nelmar/.Trash (nautilus:5982): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 2 elements at quit time (keys above) Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. (nautilus:4360): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x12bb8)! --------------------------------------------------
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 ***