GNOME Bugzilla – Bug 548463
crash in Open Folder: browsing network folders
Last modified: 2008-08-19 17:06:50 UTC
Version: 2.20.0 What were you doing when the application crashed? browsing network folders Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-486 #1 Fri Jul 18 17:03:35 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: 73326592 vsize: 73326592 resident: 29982720 share: 16003072 rss: 29982720 rss_rlim: 4294967295 CPU usage: start_time: 1219157991 rtime: 410 utime: 180 stime: 230 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 0xb6b81720 (LWP 2504)] (no debugging symbols found) 0xb7fb1430 in __kernel_vsyscall ()
+ Trace 205355
Thread 1 (Thread 0xb6b81720 (LWP 2504))
----------- .xsession-errors (78 sec old) --------------------- /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/wes-debian:/tmp/.ICE-unix/2420 ** (gnome-settings-daemon:2478): WARNING **: Failed to open file '/etc/gnome/config/General.ad': No such file or directory Window manager warning: Failed to read saved session file /home/wesley/.metacity/sessions/default0.ms: Failed to open file '/home/wesley/.metacity/sessions/default0.ms': No such file or directory Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:2504): WARNING **: Hit unhandled case 38 (Service not available) in fm_report_error_loading_directory ** (nautilus:2504): WARNING **: No description found for mime type "x-directory/smb-share" (file is "PUBLIC"), please tell the gnome-vfs mailing list. Initializing gnome-mount extension seahorse nautilus module initialized --------------------------------------------------
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 ***