GNOME Bugzilla – Bug 483548
crash in Computer:
Last modified: 2007-10-05 14:28:25 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.22.5-49.fc6 #1 SMP Thu Aug 30 14:25:46 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 110841856 vsize: 0 resident: 110841856 share: 0 rss: 38653952 rss_rlim: 0 CPU usage: start_time: 1191543867 rtime: 0 utime: 7257 stime: 0 cutime:6837 cstime: 0 timeout: 420 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 -1208670512 (LWP 6611)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 167848
Thread 1 (Thread -1208670512 (LWP 6611))
----------- .xsession-errors --------------------- Max failures exceeded, exiting now ** (nautilus:6611): CRITICAL **: nautilus_window_info_set_status: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (nautilus:6611): CRITICAL **: nautilus_window_info_set_status: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (nautilus:6611): CRITICAL **: nautilus_window_info_set_status: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (nautilus:6611): CRITICAL **: nautilus_window_info_set_status: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (nautilus:6611): CRITICAL **: nautilus_window_info_get_window_type: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (nautilus:6611): CRITICAL **: nautilus_window_info_get_ui_manager: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (bug-buddy:7096): WARNING **: Couldn't load icon for Open Folder --------------------------------------------------
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 ***