GNOME Bugzilla – Bug 378872
crash in Open Folder: Actualizando el escritor...
Last modified: 2006-11-25 12:44:46 UTC
What were you doing when the application crashed? Actualizando el escritorio con f5 Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Permissive Accessibility: Disabled ----------- .xsession-errors --------------------- /usr/share/yumex/yumexmain.py:1043: GtkWarning: file gtktreeview.c: line 6054 (do_validate_rows): assertion `gtk_tree_model_iter_next (tree_view->priv->model, &iter)' failed. There is a disparity between the internal view of the GtkTreeView, and the GtkTreeModel. This generally means that the model has changed without letting the view know. Any display from now on is likely to be incorrect. gtk.main_iteration() ** ERROR **: file nautilus-file.c: line 295 (add_to_link_hash_table_list): assertion failed: (g_list_find (list, file) == NULL) aborting... ** ERROR **: file nautilus-file.c: line 295 (add_to_link_hash_table_list): assertion failed: (g_list_find (list, file) == NULL) aborting... ** (bug-buddy:10621): WARNING **: No se pudo cargar el icono para Abrir carpeta -------------------------------------------------- Memory status: size: 121352192 vsize: 0 resident: 121352192 share: 0 rss: 29491200 rss_rlim: 0 CPU usage: start_time: 1164389073 rtime: 0 utime: 323 stime: 0 cutime:304 cstime: 0 timeout: 19 it_real_value: 0 frequency: 0 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 -1208136960 (LWP 10577)] (no debugging symbols found) 0x00476402 in __kernel_vsyscall ()
+ Trace 89050
Thread 1 (Thread -1208136960 (LWP 10577))
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 364674 ***