GNOME Bugzilla – Bug 557196
crash in Open Folder: Browsing folders on a ne...
Last modified: 2008-10-21 12:57:23 UTC
Version: 2.20.0 What were you doing when the application crashed? Browsing folders on a network system Distribution: Debian lenny/sid Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.18-6-486 #1 Tue Jun 17 20:57:16 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: 85241856 vsize: 85241856 resident: 25935872 share: 15446016 rss: 25935872 rss_rlim: 4294967295 CPU usage: start_time: 1224573658 rtime: 148 utime: 136 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) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6c46720 (LWP 2453)] (no debugging symbols found) 0xb7676321 in waitpid () from /lib/libpthread.so.0
+ Trace 208469
Thread 1 (Thread 0xb6c46720 (LWP 2453))
----------- .xsession-errors --------------------- ** Message: failed to load session from /home/ravi/.nautilus/saved-session-E2V0HU Unable to open desktop file file:///home/ravi/Desktop/nautilus.desktop for panel launcher: No such file or directory connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! ** (nautilus:2453): WARNING **: No description found for mime type "x-directory/smb-share" (file is "F"), please tell the gnome-vfs mailing list. Failed to read a valid object file image from memory. --------------------------------------------------
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 ***