GNOME Bugzilla – Bug 537986
crash in Open Folder:
Last modified: 2008-06-12 16:39:50 UTC
Version: 2.20.0 What were you doing when the application crashed? 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 Sat Apr 19 00:37:55 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 76271616 vsize: 76271616 resident: 23793664 share: 15855616 rss: 23793664 rss_rlim: 4294967295 CPU usage: start_time: 1213276326 rtime: 255 utime: 232 stime: 23 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 0xb6bdb720 (LWP 14541)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200244
Thread 1 (Thread 0xb6bdb720 (LWP 14541))
----------- .xsession-errors (36 sec old) --------------------- ** (nautilus:6700): 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!!! Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:14501): WARNING **: No description found for mime type "x-directory/smb-share" (file is "Public"), please tell the gnome-vfs mailing list. Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:14541): WARNING **: No description found for mime type "x-directory/smb-share" (file is "Public"), please tell the gnome-vfs mailing list. --------------------------------------------------
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 ***