After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 378872 - crash in Open Folder: Actualizando el escritor...
crash in Open Folder: Actualizando el escritor...
Status: RESOLVED DUPLICATE of bug 364674
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-24 17:28 UTC by miguel.palacios
Modified: 2006-11-25 12:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description miguel.palacios 2006-11-24 17:28:53 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 ()

Thread 1 (Thread -1208136960 (LWP 10577))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 nautilus_file_is_directory
  • #11 nautilus_file_is_directory
  • #12 nautilus_file_get_uri
  • #13 nautilus_file_get_uri
  • #14 nautilus_file_ref
  • #15 nautilus_directory_async_state_changed
  • #16 nautilus_directory_async_state_changed
  • #17 gnome_vfs_async_get_job_limit
    from /usr/lib/libgnomevfs-2.so.0
  • #18 gnome_vfs_async_get_job_limit
    from /usr/lib/libgnomevfs-2.so.0
  • #19 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #20 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #21 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #23 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 POA_Nautilus_MetafileMonitor__init
  • #25 __libc_start_main
    from /lib/libc.so.6
  • #26 g_cclosure_marshal_VOID__ENUM
  • #0 __kernel_vsyscall

Comment 1 Jens Granseuer 2006-11-25 12:44:46 UTC
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 ***