GNOME Bugzilla – Bug 536384
crash in Open Folder: opening a smb folder (Wi...
Last modified: 2008-06-03 10:26:05 UTC
Version: 2.20.0 What were you doing when the application crashed? opening a smb folder (Win vista with user/pass) Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Gorilla Memory status: size: 80576512 vsize: 80576512 resident: 24510464 share: 14811136 rss: 24510464 rss_rlim: 4294967295 CPU usage: start_time: 1212480750 rtime: 334 utime: 326 stime: 8 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 0xb6c10720 (LWP 4798)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 199465
Thread 1 (Thread 0xb6c10720 (LWP 4798))
----------- .xsession-errors --------------------- CALLBACK: save-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! seahorse nautilus module initialized Initializing gnome-mount extension ** (nautilus:4741): WARNING **: No description found for mime type "x-directory/smb-share" (file is "C%24"), please tell the gnome-vfs mailing list. seahorse nautilus module initialized Initializing gnome-mount extension Failed to retrieve terminal server from activation server FileList::enableItem: index out of range. (gnome-terminal:4599): Vte-WARNING **: No handler for control sequence `device-control-string' defined. ** (nautilus:4798): WARNING **: No description found for mime type "x-directory/smb-share" (file is "C%24"), 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 ***