GNOME Bugzilla – Bug 553080
crash in Open Folder: accessin remote folder i...
Last modified: 2008-09-24 09:55:37 UTC
Version: 2.20.0 What were you doing when the application crashed? accessin remote folder in a vista machine 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: Clearlooks Icon Theme: gnome Memory status: size: 108154880 vsize: 108154880 resident: 35901440 share: 16687104 rss: 35901440 rss_rlim: 4294967295 CPU usage: start_time: 1221934569 rtime: 21389 utime: 15487 stime: 5902 cutime:338 cstime: 47 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 0xb6b7b720 (LWP 2872)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 207030
Thread 1 (Thread 0xb6b7b720 (LWP 2872))
----------- .xsession-errors (13 sec old) --------------------- ** (nautilus:2872): WARNING **: bookmark uri is file:///media/ntfs/Documents%20and%20Settings/Alex/Desktop, but expected file:///media/ntfs/Documents%20and%20Settings/Alex ** (nautilus:2872): WARNING **: destroyed file has call_when_ready pending 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:2872): WARNING **: No description found for mime type "x-directory/smb-share" (file is "shared"), 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 ***