GNOME Bugzilla – Bug 531182
crash in Open Folder: opening directory
Last modified: 2008-05-03 10:16:42 UTC
Version: 2.20.0 What were you doing when the application crashed? opening directory 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 Mar 27 17:45:04 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 77918208 vsize: 77918208 resident: 25219072 share: 16162816 rss: 25219072 rss_rlim: 4294967295 CPU usage: start_time: 1209234639 rtime: 1725 utime: 1428 stime: 297 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 0xb6c0e720 (LWP 26502)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 196748
Thread 1 (Thread 0xb6c0e720 (LWP 26502))
----------- .xsession-errors --------------------- closing closing closing warning: .dynamic section for "/usr/lib/libxml2.so.2" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libatk-1.0.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libelf.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libtotem-plparser.so.10" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libedataserver-1.2.so.9" 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 ***