GNOME Bugzilla – Bug 535710
crash in Open Folder: browsed samba share
Last modified: 2008-05-30 11:17:17 UTC
Version: 2.20.0 What were you doing when the application crashed? browsed samba share 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 Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome Memory status: size: 62021632 vsize: 62021632 resident: 25677824 share: 16289792 rss: 25677824 rss_rlim: 4294967295 CPU usage: start_time: 1212142264 rtime: 305 utime: 284 stime: 21 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 0xb6b88720 (LWP 4642)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 199138
Thread 1 (Thread 0xb6b88720 (LWP 4642))
----------- .xsession-errors (9 sec old) --------------------- ** (nautilus:4601): WARNING **: No description found for mime type "x-directory/smb-share" (file is "bendras"), please tell the gnome-vfs mailing list. seahorse nautilus module initialized Initializing gnome-mount extension 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: save-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! ** (nautilus:4642): WARNING **: No description found for mime type "x-directory/smb-share" (file is "bendras"), 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 ***