GNOME Bugzilla – Bug 534449
crash in Open Folder:
Last modified: 2008-05-23 09:13:08 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu Mar 27 17:45:04 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 80486400 vsize: 80486400 resident: 24387584 share: 16781312 rss: 24387584 rss_rlim: 4294967295 CPU usage: start_time: 1211526262 rtime: 302 utime: 265 stime: 37 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 0xb6abe720 (LWP 4082)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 198437
Thread 1 (Thread 0xb6abe720 (LWP 4082))
----------- .xsession-errors --------------------- (nautilus:4082): libgnomevfs-WARNING **: Failed to create service browser: Bad state (nautilus:4082): libgnomevfs-WARNING **: Failed to create service browser: Bad state (nautilus:4082): gnome-vfs-modules-WARNING **: Failed to create client: Daemon not running ERROR: Couldn't attach to DCOP server! ** (nautilus:4082): WARNING **: Hit unhandled case 38 (Service not available) in fm_report_error_loading_directory ERROR: Couldn't attach to DCOP server! ** (nautilus:4082): WARNING **: No description found for mime type "x-directory/smb-share" (file is "patriot"), 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 ***