GNOME Bugzilla – Bug 402746
crash in Computer: Opning a folder in nauti...
Last modified: 2007-02-04 23:03:05 UTC
Version: 2.16.2 What were you doing when the application crashed? Opning a folder in nautilus uing double click 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.2868_1.fc6.cubbi_suspend2 #1 SMP Tue Dec 19 13:30:11 CET 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors --------------------- ** (nautilus:3032): CRITICAL **: nautilus_window_info_set_status: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (nautilus:3032): CRITICAL **: nautilus_window_info_set_status: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (nautilus:3032): CRITICAL **: nautilus_window_info_set_status: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (nautilus:3032): CRITICAL **: nautilus_window_info_set_status: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (nautilus:3032): CRITICAL **: nautilus_window_info_set_status: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (nautilus:3032): CRITICAL **: nautilus_window_info_get_window_type: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (nautilus:3032): CRITICAL **: nautilus_window_info_get_ui_manager: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (bug-buddy:15496): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 124014592 vsize: 0 resident: 124014592 share: 0 rss: 29417472 rss_rlim: 0 CPU usage: start_time: 1170084782 rtime: 0 utime: 2209 stime: 0 cutime:1949 cstime: 0 timeout: 260 it_real_value: 0 frequency: 162 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 -1208968448 (LWP 3032)] (no debugging symbols found) 0x009a3402 in __kernel_vsyscall ()
+ Trace 106764
Thread 1 (Thread -1208968448 (LWP 3032))
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 ***