GNOME Bugzilla – Bug 516586
crash in Home Folder: Search datas (in many fo...
Last modified: 2008-02-15 10:20:36 UTC
What were you doing when the application crashed? Search datas (in many folders,many files) Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 98603008 vsize: 98603008 resident: 39309312 share: 22708224 rss: 39309312 rss_rlim: 4294967295 CPU usage: start_time: 1203034149 rtime: 5543 utime: 2821 stime: 2722 cutime:2 cstime: 2 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 -1208531232 (LWP 2770)] [New Thread -1212138608 (LWP 2859)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 189253
Thread 2 (Thread -1212138608 (LWP 2859))
----------- .xsession-errors (62 sec old) --------------------- Starting SCIM as daemon ... Launching a SCIM process with x11... Loading socket Config module ... Creating backend ... Loading x11 FrontEnd module ... GTK Panel of SCIM 1.4.5 Starting SCIM as daemon ... SCIM has been successfully launched. Smart Common Input Method 1.4.5 SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2664 (nautilus:2770): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x1039f)! --------------------------------------------------
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 ***