GNOME Bugzilla – Bug 477003
crash in Open Folder: SEARCHING FOR FILES WITH...
Last modified: 2007-10-25 12:31:58 UTC
Version: 2.18.3 What were you doing when the application crashed? SEARCHING FOR FILES WITH ROM IN THEM 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.5-76.fc7 #1 SMP Thu Aug 30 13:08:59 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: 492666880 vsize: 492666880 resident: 47161344 share: 20922368 rss: 47161344 rss_rlim: 18446744073709551615 CPU usage: start_time: 1189794661 rtime: 2049 utime: 1682 stime: 367 cutime:123 cstime: 17 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 46912496397360 (LWP 3194)] [New Thread 1115699536 (LWP 3398)] (no debugging symbols found) 0x0000003dcf4c82e6 in poll () from /lib64/libc.so.6
+ Trace 162956
Thread 2 (Thread 1115699536 (LWP 3398))
----------- .xsession-errors (12 sec old) --------------------- 19:32:58 : Population view with packages 19:32:58 : Population Completed 19:33:12 : Getting packages : installed 19:33:12 : Found 2 installed packages 19:33:12 : Sorting packages 19:33:12 : Population view with packages 19:33:12 : Population Completed --- Hash table keys for warning below: --> file:///home/keith (nautilus:3383): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:3194): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x16c8d)! --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install the following debug packages provided by Fedora: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo. More details can be found here: http://live.gnome.org/GettingTraces
oops - this is already fixed and a duplicate of bug 454799
*** This bug has been marked as a duplicate of 454799 ***