GNOME Bugzilla – Bug 530586
crash in Open Folder: Browsing an smb share.
Last modified: 2008-04-30 08:59:55 UTC
Version: 2.20.0 What were you doing when the application crashed? Browsing an smb share. Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Fri Apr 18 23:08:22 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 433147904 vsize: 433147904 resident: 27795456 share: 17674240 rss: 27795456 rss_rlim: 18446744073709551615 CPU usage: start_time: 1209484918 rtime: 167 utime: 158 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0x2af626560240 (LWP 5165)] [New Thread 0x40800950 (LWP 5396)] 0x00002af61fe56edf in waitpid () from /lib/libpthread.so.0
+ Trace 196458
Thread 1 (Thread 0x2af626560240 (LWP 5165))
----------- .xsession-errors (25 sec old) --------------------- (gnome-panel:3394): libecal-WARNING **: e-cal.c:318: Unexpected response (evolution:4449): libecal-WARNING **: e-cal.c:318: Unexpected response (gnome-panel:3394): libecal-WARNING **: e-cal.c:318: Unexpected response (evolution:4449): libecal-WARNING **: e-cal.c:318: Unexpected response ** (nautilus:3397): WARNING **: No description found for mime type "x-directory/smb-share" (file is "eshots"), please tell the gnome-vfs mailing list. connection_message_func(): Callback CALLBACK: fill-authentication!!! Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:5165): WARNING **: No description found for mime type "x-directory/smb-share" (file is "eshots"), 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 ***