GNOME Bugzilla – Bug 462043
crash in Open Folder: seracing for a file
Last modified: 2007-07-31 21:42:28 UTC
Version: 2.18.3 What were you doing when the application crashed? seracing for a file 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: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: glass-icons Memory status: size: 100634624 vsize: 100634624 resident: 36585472 share: 20971520 rss: 36585472 rss_rlim: 4294967295 CPU usage: start_time: 1185866296 rtime: 1116 utime: 957 stime: 159 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 -1208334624 (LWP 2431)] [New Thread -1212154992 (LWP 3027)] [New Thread -1223681136 (LWP 3019)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 151755
Thread 2 (Thread -1212154992 (LWP 3027))
----------- .xsession-errors (17722 sec old) --------------------- (gnome-panel:2429): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed error getting update info: Cannot open/read repomd.xml file for repository: fedora ** Message: <info> You are now connected to the wireless network '700ap'. ** Message: <info> You are now connected to the wireless network '700ap'. --- Hash table keys for warning below: --> file:///home/ram (nautilus:2914): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:2431): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0xba9f)! --------------------------------------------------
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 ***