GNOME Bugzilla – Bug 465717
crash in Home Folder: searching for "*.iso" fr...
Last modified: 2007-08-21 20:22:44 UTC
What were you doing when the application crashed? searching for "*.iso" from the home dir. 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.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 92545024 vsize: 92545024 resident: 35377152 share: 22499328 rss: 35377152 rss_rlim: 4294967295 CPU usage: start_time: 1186851311 rtime: 579 utime: 350 stime: 229 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 -1208604960 (LWP 2479)] [New Thread -1211286640 (LWP 2642)] (no debugging symbols found) 0x00c27402 in __kernel_vsyscall ()
+ Trace 154455
Thread 2 (Thread -1211286640 (LWP 2642))
----------- .xsession-errors (8 sec old) --------------------- localuser:roger being added to access control list SESSION_MANAGER=local/casa.localdomain:/tmp/.ICE-unix/2362 winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running Initializing nautilus-image-converter extension (rhythmbox:2487): Rhythmbox-WARNING **: Unable to start mDNS browsing: O serviço MDNS não está em execução error getting update info: Cannot open/read repomd.xml file for repository: fedora (nautilus:2479): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x9b9b)! --------------------------------------------------
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 ***