GNOME Bugzilla – Bug 475658
crash in Open Folder: Using the 'search' in Na...
Last modified: 2007-09-11 09:52:14 UTC
Version: 2.18.3 What were you doing when the application crashed? Using the 'search' in Nautilus to locate a file in my personal folder. 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: Clearlooks Icon Theme: Tango Memory status: size: 166367232 vsize: 166367232 resident: 50020352 share: 36491264 rss: 50020352 rss_rlim: 4294967295 CPU usage: start_time: 1189464009 rtime: 212 utime: 170 stime: 42 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 -1208445216 (LWP 2396)] [New Thread -1254110320 (LWP 2418)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 161920
Thread 2 (Thread -1254110320 (LWP 2418))
----------- .xsession-errors (59 sec old) --------------------- package is installed and that the service is running. ** Message: failed to load session from /home/roberto/.nautilus/saved-session-WKSQXT --- Hash table keys for warning below: --> file:///home/roberto (nautilus:2364): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:2184): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x1a5c)! Initializing nautilus-search-tool extension Initializing nautilus-open-terminal extension (nautilus:2396): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x1b09)! --------------------------------------------------
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 ***