GNOME Bugzilla – Bug 483008
crash in Open Folder:
Last modified: 2007-10-05 14:32:09 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.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: Enabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 106471424 vsize: 106471424 resident: 42381312 share: 21975040 rss: 42381312 rss_rlim: 4294967295 CPU usage: start_time: 1191420879 rtime: 1900 utime: 1637 stime: 263 cutime:28 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208989984 (LWP 3347)] [New Thread -1348863088 (LWP 5610)] (no debugging symbols found) 0x00459402 in __kernel_vsyscall ()
+ Trace 167447
Thread 2 (Thread -1348863088 (LWP 5610))
----------- .xsession-errors (6 sec old) --------------------- closing GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF ** Message: Failed to close thumbnail pixbuf loader for /home/jaime/Screenshot.png: Unrecognized image file format (nautilus:3347): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x178c7)! GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized --------------------------------------------------
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 ***