GNOME Bugzilla – Bug 501594
crash in File Browser: searching a file in a nf...
Last modified: 2007-12-06 16:29:02 UTC
Version: 2.18.3 What were you doing when the application crashed? searching a file in a nfs share 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.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 138649600 vsize: 138649600 resident: 37326848 share: 26222592 rss: 37326848 rss_rlim: 4294967295 CPU usage: start_time: 1196770047 rtime: 1146 utime: 1008 stime: 138 cutime:0 cstime: 1 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 -1208211744 (LWP 2857)] [New Thread -1398043760 (LWP 5918)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 180739
Thread 2 (Thread -1398043760 (LWP 5918))
----------- .xsession-errors (7 sec old) --------------------- CConn: Using pixel format depth 24 (32bpp) little-endian rgb888 CConn: Using hextile encoding Loading "protectbase" plugin Loading "fastestmirror" plugin Loading mirror speeds from cached hostfile Could not retrieve mirrorlist http://rpm.livna.org/mirrorlist-7 error was [Errno 14] HTTP Error 404: Not Found 5 packages excluded due to repository protections Loading mirror speeds from cached hostfile Loading mirror speeds from cached hostfile closing /usr/lib/python2.5/site-packages/pirut/Progress.py:86: GtkWarning: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed self.pbar.set_fraction(fract) (nautilus:2857): 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 ***