GNOME Bugzilla – Bug 543116
crash in Open Folder: trying to browse an wind...
Last modified: 2008-07-16 07:52:41 UTC
Version: 2.20.0 What were you doing when the application crashed? trying to browse an windows share Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686 #1 SMP Fri Jun 27 03:23:20 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 79261696 vsize: 79261696 resident: 46297088 share: 15474688 rss: 46297088 rss_rlim: 4294967295 CPU usage: start_time: 1216134286 rtime: 227 utime: 215 stime: 12 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 0xb6bb2720 (LWP 5657)] (no debugging symbols found) 0xb7fd9424 in __kernel_vsyscall ()
+ Trace 202901
Thread 1 (Thread 0xb6bb2720 (LWP 5657))
----------- .xsession-errors --------------------- ** (nautilus:5603): WARNING **: No description found for mime type "x-directory/smb-share" (file is "team"), please tell the gnome-vfs mailing list. seahorse nautilus module initialized Initializing gnome-mount extension closing closing closing ** (nautilus:5626): WARNING **: No description found for mime type "x-directory/smb-share" (file is "team"), please tell the gnome-vfs mailing list. seahorse nautilus module initialized Initializing gnome-mount extension seahorse nautilus module initialized Initializing gnome-mount extension ** (nautilus:5657): WARNING **: No description found for mime type "x-directory/smb-share" (file is "team"), 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 ***