GNOME Bugzilla – Bug 492878
crash in Open Folder: searching a directory fo...
Last modified: 2007-11-03 01:43:56 UTC
Version: 2.18.3 What were you doing when the application crashed? searching a directory for a 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 96157696 vsize: 96157696 resident: 26034176 share: 20217856 rss: 26034176 rss_rlim: 4294967295 CPU usage: start_time: 1194048226 rtime: 432 utime: 387 stime: 45 cutime:64 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 -1208568096 (LWP 2716)] [New Thread -1273607280 (LWP 3160)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 174739
Thread 2 (Thread -1273607280 (LWP 3160))
----------- .xsession-errors --------------------- Reusing existing ksycoca kbuildsycoca running... Reusing existing ksycoca kbuildsycoca running... Reusing existing ksycoca kbuildsycoca running... Reusing existing ksycoca ASSERT: "quotient.m_denom != 0" in mymoneymoney.cpp (496) ASSERT: "quotient.m_denom != 0" in mymoneymoney.cpp (496) ASSERT: "quotient.m_denom != 0" in mymoneymoney.cpp (496) ASSERT: "quotient.m_denom != 0" in mymoneymoney.cpp (496) ICE default IO error handler doing an exit(), pid = 3001, errno = 0 (nautilus:2716): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x41f8)! --------------------------------------------------
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 ***