GNOME Bugzilla – Bug 490656
crash in Open Folder: searching. nothing else...
Last modified: 2007-10-27 11:20:42 UTC
Version: 2.18.3 What were you doing when the application crashed? searching. nothing else. 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.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Clearlooks Memory status: size: 425439232 vsize: 425439232 resident: 40189952 share: 27189248 rss: 40189952 rss_rlim: 18446744073709551615 CPU usage: start_time: 1193433544 rtime: 452 utime: 361 stime: 91 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496454704 (LWP 3047)] [New Thread 1084229968 (LWP 3058)] (no debugging symbols found) 0x00000039254c82e6 in poll () from /lib64/libc.so.6
+ Trace 173129
Thread 2 (Thread 1084229968 (LWP 3058))
----------- .xsession-errors --------------------- error getting update info: Cannot retrieve repository metadata (repomd.xml) for repository: livna. Please verify its path and try again (nautilus:2543): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x792e)! (bug-buddy:3010): GLib-GObject-WARNING **: invalid uninstantiatable type `motion-notify-event' in cast to `GObject' (bug-buddy:3010): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (bug-buddy:3010): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:3010): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:3047): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x74c5)! --------------------------------------------------
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 ***