GNOME Bugzilla – Bug 449045
crash in Open Folder:
Last modified: 2007-06-22 22:06:57 UTC
Version: 2.16.2 What were you doing when the application crashed? Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.20-1.2952.fc6 #1 SMP Wed May 16 18:59:18 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000001 Selinux: No Accessibility: Disabled Memory status: size: 104124416 vsize: 0 resident: 104124416 share: 0 rss: 31272960 rss_rlim: 0 CPU usage: start_time: 1182149802 rtime: 0 utime: 3561 stime: 0 cutime:2612 cstime: 0 timeout: 949 it_real_value: 0 frequency: 33 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 -1208677632 (LWP 3273)] (no debugging symbols found) 0x00821402 in __kernel_vsyscall ()
+ Trace 142082
Thread 1 (Thread -1208677632 (LWP 3273))
----------- .xsession-errors --------------------- (nautilus:3273): Gtk-CRITICAL **: update_node: assertion `node != NULL' failed (nautilus:3273): Gtk-CRITICAL **: gtk_widget_realize: assertion `GTK_WIDGET_ANCHORED (widget) || GTK_IS_INVISIBLE (widget)' failed ** (nautilus:3273): CRITICAL **: nautilus_window_info_set_status: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (nautilus:3273): CRITICAL **: nautilus_window_info_set_status: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (nautilus:3273): CRITICAL **: nautilus_window_info_get_window_type: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (nautilus:3273): CRITICAL **: nautilus_window_info_get_ui_manager: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (bug-buddy:31318): WARNING **: Impossibile caricare l'icona per Apri cartella ** (bug-buddy:31318): WARNING **: Impossibile caricare l'icona per Cerca file... --------------------------------------------------
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 374002 ***