GNOME Bugzilla – Bug 543949
crash in Open Folder: Trying to view contents ...
Last modified: 2008-07-21 09:03:10 UTC
Version: 2.20.0 What were you doing when the application crashed? Trying to view contents of a SMB share on a Windows XP host Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686 #1 SMP Fri Jun 27 03:23:20 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: 54501376 vsize: 54501376 resident: 28766208 share: 16248832 rss: 28766208 rss_rlim: 4294967295 CPU usage: start_time: 1216623507 rtime: 492 utime: 262 stime: 230 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6ab6710 (LWP 2057)] (no debugging symbols found) 0xb7efa424 in __kernel_vsyscall ()
+ Trace 203377
Thread 1 (Thread 0xb6ab6710 (LWP 2057))
----------- .xsession-errors --------------------- ** (nautilus:1991): WARNING **: No description found for mime type "x-directory/smb-share" (file is "downloads"), please tell the gnome-vfs mailing list. Initializing gnome-mount extension seahorse nautilus module initialized ** (gedit:2065): WARNING **: Could not load gedit state file: File is empty ** (nautilus:2057): 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!!! ** (nautilus:2057): WARNING **: No description found for mime type "x-directory/smb-share" (file is "downloads"), 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 ***