GNOME Bugzilla – Bug 545778
crash in Open Folder: attempting to open share...
Last modified: 2008-08-01 08:15:37 UTC
Version: 2.20.0 What were you doing when the application crashed? attempting to open shared folder on Windows (XP Home/SP3) Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-486 #1 Sun Feb 10 19:36:16 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: 78102528 vsize: 78102528 resident: 25894912 share: 14974976 rss: 25894912 rss_rlim: 4294967295 CPU usage: start_time: 1217551039 rtime: 256 utime: 235 stime: 21 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 0xb6bc4720 (LWP 10605)] [New Thread 0xb4b89b90 (LWP 10627)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 204321
Thread 1 (Thread 0xb6bc4720 (LWP 10605))
----------- .xsession-errors --------------------- ** (epiphany-browser:2551): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed ** (nautilus:2424): WARNING **: Hit unhandled case 38 (Service not available) in fm_report_error_loading_directory connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! Initializing gnome-mount extension seahorse nautilus module initialized Initializing gnome-mount extension seahorse nautilus module initialized Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:10605): WARNING **: No description found for mime type "x-directory/smb-share" (file is "SharedDocs"), 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 ***