GNOME Bugzilla – Bug 539931
crash in Open Folder: I was using smb to conne...
Last modified: 2008-06-24 13:00:50 UTC
Version: 2.20.0 What were you doing when the application crashed? I was using smb to connect to a remote computer and simultaneously updating my debian machine 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: Mist Memory status: size: 87101440 vsize: 87101440 resident: 36601856 share: 16035840 rss: 36601856 rss_rlim: 4294967295 CPU usage: start_time: 1214305942 rtime: 1455 utime: 1353 stime: 102 cutime:0 cstime: 2 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 0xb6bfd720 (LWP 3470)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 201251
Thread 1 (Thread 0xb6bfd720 (LWP 3470))
----------- .xsession-errors --------------------- CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! ** (nautilus:3470): WARNING **: No description found for mime type "x-directory/smb-share" (file is "C%24"), please tell the gnome-vfs mailing list. warning: .dynamic section for "/usr/lib/libnss3.so.1d" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libnssutil3.so.1d" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libssl3.so.1d" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
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 ***