GNOME Bugzilla – Bug 513908
crash in Computer: Je venais de fermer une ...
Last modified: 2008-02-02 19:00:30 UTC
Version: 2.20.0 What were you doing when the application crashed? Je venais de fermer une fenêtre. Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 151343104 vsize: 151343104 resident: 66854912 share: 17268736 rss: 66854912 rss_rlim: 4294967295 CPU usage: start_time: 1201945595 rtime: 16040 utime: 8392 stime: 7648 cutime:12913 cstime: 1601 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 0xb6b9b6c0 (LWP 3688)] [New Thread 0xb19ffb90 (LWP 23171)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187848
Thread 1 (Thread 0xb6b9b6c0 (LWP 3688))
----------- .xsession-errors --------------------- GetBoundingMetrics (char *) GetBoundingMetrics (char *) GetBoundingMetrics (char *) GetBoundingMetrics (char *) GetBoundingMetrics (char *) GetBoundingMetrics (char *) (nautilus:3688): Gtk-CRITICAL **: gtk_tree_model_sort_real_unref_node: assertion `elt->ref_count > 0' failed ** ERROR **: file fm-tree-model.c: line 1531 (fm_tree_model_unref_node): assertion failed: (node->ref_count > 0) aborting... warning: .dynamic section for "/usr/lib/libexempi.so.3" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
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 459221 ***