GNOME Bugzilla – Bug 470669
crash in Open Folder: Searched for files of ty...
Last modified: 2007-09-05 15:37:28 UTC
Version: 2.18.3 What were you doing when the application crashed? Searched for files of type "ICO icon" 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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 99078144 vsize: 99078144 resident: 35557376 share: 20586496 rss: 35557376 rss_rlim: 4294967295 CPU usage: start_time: 1188214302 rtime: 1061 utime: 953 stime: 108 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 -1208359200 (LWP 3001)] [New Thread -1220949104 (LWP 3219)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 158169
Thread 2 (Thread -1220949104 (LWP 3219))
----------- .xsession-errors (9 sec old) --------------------- localuser:root being added to access control list SESSION_MANAGER=local/msi.home.ch:/tmp/.ICE-unix/2878 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. 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. Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x1000950 (.gnome2); these messages lack timestamps and therefore suck. (nautilus:3001): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x126cf)! --------------------------------------------------
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 ***