GNOME Bugzilla – Bug 521580
crash in Open Folder: Searching for a file
Last modified: 2008-03-10 20:43:49 UTC
Version: 2.18.3 What were you doing when the application crashed? Searching for a file 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.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 101584896 vsize: 101584896 resident: 38019072 share: 23945216 rss: 38019072 rss_rlim: 4294967295 CPU usage: start_time: 1204577973 rtime: 7889 utime: 6703 stime: 1186 cutime:873 cstime: 114 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 -1208441120 (LWP 2626)] [New Thread -1297613936 (LWP 8329)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 191970
Thread 2 (Thread -1297613936 (LWP 8329))
----------- .xsession-errors (6 sec old) --------------------- XS[src/xmms-sid.c:xs_reinit:177]: init#1: OK, 1 XS[src/xmms-sid.c:xs_reinit:189]: init#2: OK, 0 XS[src/xmms-sid.c:xs_init:226]: OK camel-Message: -- camel-Message: -- Autoselected keyboard map en-us ERROR: recv: Connection reset by peer --- Hash table keys for warning below: --> file:///home/cporter (nautilus:8271): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) Window manager warning: Invalid WM_TRANSIENT_FOR window 0x88 specified for 0x14199c6 (). (nautilus:2626): 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 ***