GNOME Bugzilla – Bug 541124
crash in Open Folder: Opening a folder on a re...
Last modified: 2008-07-01 19:29:11 UTC
Version: 2.20.0 What were you doing when the application crashed? Opening a folder on a recently created samba share on a PC running WinXP Pro. 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: Glossy Icon Theme: Nuvola Memory status: size: 101244928 vsize: 101244928 resident: 30330880 share: 17047552 rss: 30330880 rss_rlim: 4294967295 CPU usage: start_time: 1214937628 rtime: 533 utime: 506 stime: 27 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 0xb6b72720 (LWP 3913)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 201855
Thread 1 (Thread 0xb6b72720 (LWP 3913))
----------- .xsession-errors --------------------- seahorse nautilus module initialized Initializing gnome-mount extension /usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet warnings.warn("apt API not stable yet", FutureWarning) current dist not found in meta-release file connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:3913): WARNING **: No description found for mime type "x-directory/smb-share" (file is "Dokumenty"), please tell the gnome-vfs mailing list. warning: .dynamic section for "/usr/lib/libfreetype.so.6" 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 ***