GNOME Bugzilla – Bug 531866
crash in Open Folder: Browsing shares on a Win...
Last modified: 2008-05-07 08:47:00 UTC
Version: 2.20.0 What were you doing when the application crashed? Browsing shares on a Windows computer (C$). Other shares were accessible. 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 Sat Apr 19 00:37:55 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: 74993664 vsize: 74993664 resident: 28291072 share: 16113664 rss: 28291072 rss_rlim: 4294967295 CPU usage: start_time: 1210124033 rtime: 500 utime: 474 stime: 26 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 0xb6bc1720 (LWP 3509)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 197091
Thread 1 (Thread 0xb6bc1720 (LWP 3509))
----------- .xsession-errors (46 sec old) --------------------- /usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet warnings.warn("apt API not stable yet", FutureWarning) current dist not found in meta-release file connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:3194): WARNING **: No description found for mime type "x-directory/smb-share" (file is "My%20Documents"), please tell the gnome-vfs mailing list. seahorse nautilus module initialized Initializing gnome-mount extension ** (nautilus:3509): WARNING **: No description found for mime type "x-directory/smb-share" (file is "F%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 ***