GNOME Bugzilla – Bug 502252
crash in Open Folder: searching
Last modified: 2007-12-07 16:53:40 UTC
Version: 2.18.3 What were you doing when the application crashed? searching 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.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 96194560 vsize: 96194560 resident: 39903232 share: 22425600 rss: 39903232 rss_rlim: 4294967295 CPU usage: start_time: 1196942005 rtime: 2247 utime: 1700 stime: 547 cutime:58 cstime: 8 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 -1208416544 (LWP 3010)] [New Thread -1221006448 (LWP 20539)] (no debugging symbols found) 0x0034c402 in __kernel_vsyscall ()
+ Trace 181069
Thread 2 (Thread -1221006448 (LWP 20539))
----------- .xsession-errors (9 sec old) --------------------- --- Hash table keys for warning below: --> file:///home/pushkin (nautilus:20395): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) error: The metadata does not have a thumbnail property error: The metadata does not have a thumbnail property --- Hash table keys for warning below: --> file:///home/pushkin (nautilus:20503): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:3010): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x16cb9)! Xlib: sequence lost (0x200a7 > 0x16df7) in reply type 0xe1! --------------------------------------------------
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 ***