GNOME Bugzilla – Bug 464164
crash in Open Folder:
Last modified: 2007-08-07 13:45:24 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: No Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 104366080 vsize: 104366080 resident: 41914368 share: 26980352 rss: 41914368 rss_rlim: 4294967295 CPU usage: start_time: 1186439962 rtime: 1292 utime: 1161 stime: 131 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 -1208142112 (LWP 2863)] [New Thread -1210242160 (LWP 3697)] (no debugging symbols found) 0x00110402 in ?? () from /lib/libcrypto.so.6
+ Trace 153323
Thread 2 (Thread -1210242160 (LWP 3697))
----------- .xsession-errors --------------------- Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". (nautilus:2863): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". warning: .dynamic section for "/lib/libssl.so.6" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/lib/libcrypto.so.6" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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 ***