GNOME Bugzilla – Bug 535736
crash in Open Folder:
Last modified: 2008-05-30 12:29:23 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (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: 79605760 vsize: 79605760 resident: 26681344 share: 16740352 rss: 26681344 rss_rlim: 4294967295 CPU usage: start_time: 1212132171 rtime: 704 utime: 600 stime: 104 cutime:12 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 0xb6b93720 (LWP 3101)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 199159
Thread 1 (Thread 0xb6b93720 (LWP 3101))
----------- .xsession-errors --------------------- ** Message: GetValue variable 2 (2) ** (nautilus:3101): WARNING **: Ingen beskrivelse funnet for MIME-type «x-directory/smb-share» (fil «asle»), si i fra til gnome-vfs e-post listen. connection_message_func(): Callback CALLBACK: fill-authentication!!! warning: .dynamic section for "/usr/lib/libgnome-menu.so.2" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libgnutls.so.26" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libXau.so.6" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libXxf86vm.so.1" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libnss3.so.1d" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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 ***