GNOME Bugzilla – Bug 461930
crash in Open Folder: searching for a file in ...
Last modified: 2007-07-31 21:43:00 UTC
Version: 2.18.3 What were you doing when the application crashed? searching for a file in the file browser 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-33.fc7 #1 SMP Mon Jul 23 17:33:07 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: 82788352 vsize: 82788352 resident: 29831168 share: 20803584 rss: 29831168 rss_rlim: 4294967295 CPU usage: start_time: 1185650541 rtime: 241 utime: 201 stime: 40 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 -1209092384 (LWP 3213)] [New Thread -1221682288 (LWP 3743)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 151681
Thread 2 (Thread -1221682288 (LWP 3743))
----------- .xsession-errors (11 sec old) --------------------- Checking for GLX_EXT_texture_from_pixmap : passed Checking for non power of two texture support : passed Checking maximum texture size : passed (2048x2048) error getting update info: Cannot open/read repomd.xml file for repository: fedora ** Message: <info> You are now connected to the wireless network 'TURBONETT'. --- Hash table keys for warning below: --> file:///home/huevo (nautilus:3711): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:3213): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x2de2)! --------------------------------------------------
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 ***