GNOME Bugzilla – Bug 489309
crash in Open Folder:
Last modified: 2007-10-23 10:44:15 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.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 533549056 vsize: 533549056 resident: 44216320 share: 20451328 rss: 44216320 rss_rlim: 18446744073709551615 CPU usage: start_time: 1193122907 rtime: 11888 utime: 9858 stime: 2030 cutime:6 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496364592 (LWP 2985)] [New Thread 1136814416 (LWP 6273)] (no debugging symbols found) 0x00000031a2ac82e6 in poll () from /lib64/libc.so.6
+ Trace 172156
Thread 2 (Thread 1136814416 (LWP 6273))
----------- .xsession-errors (7 sec old) --------------------- JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] --- Hash table keys for warning below: --> file:///home/tim (nautilus:5976): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:2985): Gtk-CRITICAL **: gtk_window_realize_icon: assertion `info->icon_pixmap == NULL' failed JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] (nautilus:2985): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x20b720)! --------------------------------------------------
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 ***