GNOME Bugzilla – Bug 538646
crash in Open Folder: Closing the window
Last modified: 2008-06-16 18:28:44 UTC
Version: 2.20.0 What were you doing when the application crashed? Closing the window 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: Gorilla Icon Theme: Gorilla Memory status: size: 84434944 vsize: 84434944 resident: 31293440 share: 16449536 rss: 31293440 rss_rlim: 4294967295 CPU usage: start_time: 1213642346 rtime: 728 utime: 684 stime: 44 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 0xb6bda720 (LWP 3768)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200590
Thread 1 (Thread 0xb6bda720 (LWP 3768))
----------- .xsession-errors --------------------- Deinitializing plugins... ** ** ERROR:(fm-tree-model.c:1527):fm_tree_model_unref_node: assertion failed: (parent->dummy_child_ref_count > 0) warning: .dynamic section for "/usr/lib/libdbus-glib-1.so.2" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libfam.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libplds4.so.0d" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libplc4.so.0d" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libnspr4.so.0d" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 512040 ***