GNOME Bugzilla – Bug 473897
crash in Open Folder: searching for files
Last modified: 2007-09-05 15:34:42 UTC
Version: 2.18.3 What were you doing when the application crashed? searching for files 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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 146640896 vsize: 146640896 resident: 49307648 share: 33951744 rss: 49307648 rss_rlim: 4294967295 CPU usage: start_time: 1188996074 rtime: 470 utime: 296 stime: 174 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 -1208375584 (LWP 3514)] [New Thread -1350804592 (LWP 3845)] (no debugging symbols found) 0x0050b402 in __kernel_vsyscall ()
+ Trace 160631
Thread 2 (Thread -1350804592 (LWP 3845))
----------- .xsession-errors (10 sec old) --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) --- Hash table keys for warning below: --> file:///home/chris (nautilus:3820): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:3514): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x3a3f)! --------------------------------------------------
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 ***