GNOME Bugzilla – Bug 468592
crash in Open Folder:
Last modified: 2007-08-21 20:26:17 UTC
Version: 2.18.3 What were you doing when the application crashed? 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: 101031936 vsize: 101031936 resident: 36843520 share: 21114880 rss: 36843520 rss_rlim: 4294967295 CPU usage: start_time: 1187629254 rtime: 683 utime: 627 stime: 56 cutime:0 cstime: 1 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 -1208838432 (LWP 3114)] [New Thread -1263539312 (LWP 3194)] [New Thread -1210938480 (LWP 3161)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 156627
Thread 2 (Thread -1263539312 (LWP 3194))
----------- .xsession-errors --------------------- (nautilus:3090): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x1c6b)! --- Hash table keys for warning below: --> file:///home/alex (nautilus:3123): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) --- Hash table keys for warning below: --> file:///home/alex (nautilus:3184): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:3114): 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 ***