GNOME Bugzilla – Bug 466365
crash in Open Folder: searching for file
Last modified: 2007-08-21 20:28:25 UTC
Version: 2.18.3 What were you doing when the application crashed? searching for file 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:21:43 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome Memory status: size: 489594880 vsize: 489594880 resident: 47968256 share: 20267008 rss: 47968256 rss_rlim: 18446744073709551615 CPU usage: start_time: 1187018538 rtime: 6192 utime: 5422 stime: 770 cutime:19 cstime: 11 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 46912496385072 (LWP 3049)] [New Thread 1105209680 (LWP 20461)] (no debugging symbols found) 0x00000033898c82e6 in poll () from /lib64/libc.so.6
+ Trace 154962
Thread 2 (Thread 1105209680 (LWP 20461))
----------- .xsession-errors (20 sec old) --------------------- *** (../../gui/shared/utils/io.cpp:190) *** 'DJVU::GUTF8String ReadString(int, int, void (*)())' *** PIPE *** (../../gui/shared/utils/io.cpp:190) *** 'DJVU::GUTF8String ReadString(int, int, void (*)())' *** /usr/local/seamonkey114/run-mozilla.sh: line 131: 5825 Killed "$prog" ${1+"$@"} PIPE *** (../../gui/shared/utils/io.cpp:100) *** 'void Read(int, void*, int, int, void (*)())' (nautilus:3049): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x194e34)! --------------------------------------------------
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 ***