GNOME Bugzilla – Bug 536618
crash in Open Folder: Browsing an samba share ...
Last modified: 2008-06-05 00:00:07 UTC
Version: 2.20.0 What were you doing when the application crashed? Browsing an samba share on my webserver Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686 #1 SMP Wed May 14 16:42:03 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: 74428416 vsize: 74428416 resident: 28676096 share: 15704064 rss: 28676096 rss_rlim: 4294967295 CPU usage: start_time: 1212592332 rtime: 194 utime: 184 stime: 10 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 0xb6b9d720 (LWP 3676)] [New Thread 0xb5f58b90 (LWP 3702)] [New Thread 0xb55ffb90 (LWP 3700)] (no debugging symbols found) 0xb7f49424 in __kernel_vsyscall ()
+ Trace 199566
Thread 1 (Thread 0xb6b9d720 (LWP 3676))
----------- .xsession-errors (7 sec old) --------------------- ** (nautilus:3051): WARNING **: No description found for mime type "x-directory/smb-share" (file is "moya"), 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: save-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! seahorse nautilus module initialized Initializing gnome-mount extension ** (nautilus:3676): WARNING **: No description found for mime type "x-directory/smb-share" (file is "moya"), 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 ***