GNOME Bugzilla – Bug 491616
crash in Home Folder: playing Gnome card games...
Last modified: 2007-10-30 09:48:57 UTC
What were you doing when the application crashed? playing Gnome card games...Searching for photos... 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: Crux Icon Theme: Crux Memory status: size: 159948800 vsize: 159948800 resident: 35000320 share: 20885504 rss: 35000320 rss_rlim: 4294967295 CPU usage: start_time: 1193663481 rtime: 10563 utime: 8895 stime: 1668 cutime:367 cstime: 46 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 -1208523040 (LWP 2921)] [New Thread -1353266288 (LWP 12992)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 173836
Thread 2 (Thread -1353266288 (LWP 12992))
----------- .xsession-errors (24 sec old) --------------------- could not load face 'file:///media/Yijian%20Xu's%20HD/System%20Volume%20Information/_restore%7B5B942C52-3EC6-4393-ADAF-2DA421A20CCE%7D/RP121/change.log.1': broken file ** (stardict:3495): WARNING **: Error, selection data didn't received, retring! ** (stardict:3495): WARNING **: Error, selection data didn't received, retring! ** (stardict:3495): WARNING **: Error, selection data didn't received, retring! ** (stardict:3495): WARNING **: Error, selection data didn't received, retring! (nautilus:2921): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed --------------------------------------------------
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 ***