GNOME Bugzilla – Bug 466441
crash in Home Folder: pesquisando o termo: *.p...
Last modified: 2007-08-21 20:22:48 UTC
What were you doing when the application crashed? pesquisando o termo: *.ps 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 94494720 vsize: 94494720 resident: 37224448 share: 21512192 rss: 37224448 rss_rlim: 4294967295 CPU usage: start_time: 1187055323 rtime: 880 utime: 700 stime: 180 cutime:0 cstime: 0 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 -1208232224 (LWP 3050)] [New Thread -1242383472 (LWP 3311)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 155019
Thread 2 (Thread -1242383472 (LWP 3311))
----------- .xsession-errors (6 sec old) --------------------- Requested buffer size 32768, fragment size 8192 ALSA pcm 'default' set buffer size 33868, period size 3760 bytes Requested buffer size 32768, fragment size 8192 ALSA pcm 'default' set buffer size 33868, period size 3760 bytes Requested buffer size 32768, fragment size 8192 ALSA pcm 'default' set buffer size 33868, period size 3760 bytes Playing time: ~7 seconds Notes cut: 0 Notes lost totally: 0 Requested buffer size 32768, fragment size 8192 ALSA pcm 'default' set buffer size 33868, period size 3760 bytes Requested buffer size 32768, fragment size 8192 ALSA pcm 'default' set buffer size 33868, period size 3760 bytes (nautilus:3050): 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 ***