GNOME Bugzilla – Bug 537469
crash in Open Folder: browsing samba shares fr...
Last modified: 2008-06-09 22:20:53 UTC
Version: 2.20.0 What were you doing when the application crashed? browsing samba shares from a MS Domain 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: black-white_2-Neon Memory status: size: 97792000 vsize: 97792000 resident: 32157696 share: 18378752 rss: 32157696 rss_rlim: 4294967295 CPU usage: start_time: 1213014408 rtime: 1701 utime: 1573 stime: 128 cutime:8 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6b2a720 (LWP 4109)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 199967
Thread 1 (Thread 0xb6b2a720 (LWP 4109))
----------- .xsession-errors --------------------- CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x1405144 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/gnome-vfs-2.0/modules/libfile.so" 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 ***