GNOME Bugzilla – Bug 525645
crash in Open Folder: Navigating a windows sha...
Last modified: 2008-04-04 10:28:26 UTC
Version: 2.20.0 What were you doing when the application crashed? Navigating a windows share Distribution: Debian lenny/sid Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: T-ish-Ubuntulooks Icon Theme: OSX Memory status: size: 58884096 vsize: 58884096 resident: 26034176 share: 14712832 rss: 26034176 rss_rlim: 4294967295 CPU usage: start_time: 1207083448 rtime: 185 utime: 170 stime: 15 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b3d720 (LWP 4366)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 193942
Thread 1 (Thread 0xb6b3d720 (LWP 4366))
----------- .xsession-errors (10 sec old) --------------------- seahorse nautilus module initialized Initializing gnome-mount extension ** (nautilus:3401): WARNING **: Hit unhandled case 46 (Timeout reached) in fm_report_error_loading_directory connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! seahorse nautilus module initialized Initializing gnome-mount extension connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! --------------------------------------------------
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 525181 ***