GNOME Bugzilla – Bug 471558
crash in File Browser: eseguendo una ricerca
Last modified: 2007-08-30 17:07:39 UTC
Version: 2.18.3 What were you doing when the application crashed? eseguendo una ricerca 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: Industrial Icon Theme: OSX Memory status: size: 92991488 vsize: 92991488 resident: 34930688 share: 22061056 rss: 34930688 rss_rlim: 4294967295 CPU usage: start_time: 1188419484 rtime: 470 utime: 406 stime: 64 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 -1208158496 (LWP 5064)] [New Thread -1221174384 (LWP 5087)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 158856
Thread 2 (Thread -1221174384 (LWP 5087))
----------- .xsession-errors (7 sec old) --------------------- --> file:///home/fabio (nautilus:5038): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) ** (tsclient:4789): WARNING **: Autoselected keyboard map it ERROR: 192.168.1.198: unable to connect (nautilus:3094): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x3f148)! (nautilus:5064): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x2ddf)! --------------------------------------------------
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 ***