GNOME Bugzilla – Bug 563107
crash in File Browser: navegar por una carpeta ...
Last modified: 2008-12-03 13:48:14 UTC
Version: 2.20.0 What were you doing when the application crashed? navegar por una carpeta de red Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26 #1 SMP Sat Oct 25 19:34:26 CEST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 94511104 vsize: 94511104 resident: 39669760 share: 17432576 rss: 39669760 rss_rlim: 4294967295 CPU usage: start_time: 1228301490 rtime: 2943 utime: 2339 stime: 604 cutime:16 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xb6b309a0 (LWP 3849)] 0xb802e424 in __kernel_vsyscall ()
+ Trace 210445
Thread 1 (Thread 0xb6b309a0 (LWP 3849))
----------- .xsession-errors (6 sec old) --------------------- (vmware:5742): libgnomevfs-CRITICAL **: gnome_vfs_uri_unref: assertion `uri != NULL' failed ** ** ERROR:(fm-tree-model.c:1531):fm_tree_model_unref_node: assertion failed: (node->ref_count > 0) warning: .dynamic section for "/usr/lib/libxml2.so.2" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libORBit-2.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libfontconfig.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libORBitCosNaming-2.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libXi.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 512040 ***