GNOME Bugzilla – Bug 558890
crash in Open Folder: Attempting to open a sha...
Last modified: 2008-11-02 11:33:22 UTC
Version: 2.20.0 What were you doing when the application crashed? Attempting to open a share on a Windows XP based system Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 78553088 vsize: 78553088 resident: 24682496 share: 15732736 rss: 24682496 rss_rlim: 4294967295 CPU usage: start_time: 1225604352 rtime: 1840 utime: 1698 stime: 142 cutime:0 cstime: 1 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 0xb6b30720 (LWP 6884)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 209079
Thread 1 (Thread 0xb6b30720 (LWP 6884))
----------- .xsession-errors (68 sec old) --------------------- CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:6884): WARNING **: Hit unhandled case 31 (Operation cancelled) in fm_report_error_loading_directory connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 522534 ***