GNOME Bugzilla – Bug 539083
crash in Open Folder: Trying to open a folder ...
Last modified: 2008-06-19 07:44:16 UTC
Version: 2.20.0 What were you doing when the application crashed? Trying to open a folder on a samba share on another Debian machine on the local network Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 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: 82071552 vsize: 82071552 resident: 27299840 share: 16437248 rss: 27299840 rss_rlim: 4294967295 CPU usage: start_time: 1213855524 rtime: 268 utime: 253 stime: 15 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 0xb6baf720 (LWP 8778)] [New Thread 0xb2dfbb90 (LWP 8808)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200828
Thread 1 (Thread 0xb6baf720 (LWP 8778))
----------- .xsession-errors (7 sec old) --------------------- CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! warning: .dynamic section for "/usr/lib/libdbus-glib-1.so.2" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:8778): WARNING **: No description found for mime type "x-directory/smb-share" (file is "sda5"), 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 ***