GNOME Bugzilla – Bug 531157
crash in Open Folder: was reading files from a...
Last modified: 2008-05-03 19:53:21 UTC
Version: 2.20.0 What were you doing when the application crashed? was reading files from another computer who uses windows Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 72921088 vsize: 72921088 resident: 26701824 share: 15998976 rss: 26701824 rss_rlim: 4294967295 CPU usage: start_time: 1209761734 rtime: 369 utime: 337 stime: 32 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 0xb6b80720 (LWP 4104)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 196732
Thread 1 (Thread 0xb6b80720 (LWP 4104))
----------- .xsession-errors (12 sec old) --------------------- CALLBACK: fill-authentication!!! ** (nautilus:4104): WARNING **: No description found for mime type "x-directory/smb-share" (file is "C%24"), please tell the gnome-vfs mailing list. connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:4104): WARNING **: Hit unhandled case 31 (Operation cancelled) in fm_report_error_loading_directory --------------------------------------------------
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 ***
*** Bug 531272 has been marked as a duplicate of this bug. ***