GNOME Bugzilla – Bug 470361
crash in Open Folder: I was just trying to sea...
Last modified: 2007-09-05 15:37:17 UTC
Version: 2.18.3 What were you doing when the application crashed? I was just trying to search something I looked for, that's all 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: Clearlooks Icon Theme: Fedora Memory status: size: 144248832 vsize: 144248832 resident: 46190592 share: 24477696 rss: 46190592 rss_rlim: 4294967295 CPU usage: start_time: 1188105919 rtime: 6851 utime: 5406 stime: 1445 cutime:105 cstime: 15 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 -1208842528 (LWP 2442)] [New Thread -1263391856 (LWP 3167)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 157949
Thread 2 (Thread -1263391856 (LWP 3167))
----------- .xsession-errors (7 sec old) --------------------- Error: Couldn't find a font for 'Ryumin-Light-Identity-H' Error: Couldn't find a font for 'Ryumin-Light-Identity-H' Error: Couldn't find a font for 'Ryumin-Light-Identity-H' Error: Couldn't find a font for 'Ryumin-Light-Identity-H' Error: Couldn't find a font for 'GothicBBB-Medium-Identity-H' Error: Couldn't find a font for 'Ryumin-Light-Identity-H' Error: Couldn't find a font for 'Ryumin-Light-Identity-H' Error: Couldn't find a font for 'Ryumin-Light-Identity-H' Error: Couldn't find a font for 'Ryumin-Light-Identity-H' Error: Couldn't find a font for 'Ryumin-Light-Identity-H' XtUngrabButton(drawArea,3,0) Warning: Attempt to remove nonexistent passive grab (nautilus:2442): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x44dea)! --------------------------------------------------
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 ***