GNOME Bugzilla – Bug 539069
crash in Open Folder: Tryng to view a hidden s...
Last modified: 2008-06-19 07:45:16 UTC
Version: 2.20.0 What were you doing when the application crashed? Tryng to view a hidden share C$ on a Windows XP SP2 computer. After filling in the user credentials at the login prompt Nautilius crashed. Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (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: 85188608 vsize: 85188608 resident: 30064640 share: 16592896 rss: 30064640 rss_rlim: 4294967295 CPU usage: start_time: 1213845697 rtime: 400 utime: 371 stime: 29 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 0xb6b9b720 (LWP 2815)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200821
Thread 1 (Thread 0xb6b9b720 (LWP 2815))
----------- .xsession-errors --------------------- (nautilus:2815): gnome-vfs-modules-WARNING **: Failed to create client: Daemon not running 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:2815): 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 ***