GNOME Bugzilla – Bug 534191
crash in File Browser: abriendo el navegador
Last modified: 2008-05-21 23:27:42 UTC
Version: 2.20.0 What were you doing when the application crashed? abriendo el navegador Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-486 #1 Sun Feb 10 19:36:16 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Nuvola Icon Theme: Nuvola Memory status: size: 91430912 vsize: 91430912 resident: 25526272 share: 13606912 rss: 25526272 rss_rlim: 4294967295 CPU usage: start_time: 1211374471 rtime: 1926 utime: 1765 stime: 161 cutime:147 cstime: 26 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 0xb6b92720 (LWP 2644)] [New Thread 0xb6340b90 (LWP 16270)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 198305
----------- .xsession-errors (7 sec old) --------------------- Error: Top-level pages object is wrong type (null) Error: Couldn't read page catalog ** ERROR **: file fm-tree-model.c: line 1527 (fm_tree_model_unref_node): assertion failed: (parent->dummy_child_ref_count > 0) aborting... warning: .dynamic section for "/usr/lib/libgdk_pixbuf-2.0.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libglib-2.0.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libcroco-0.6.so.3" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libgnutls.so.26" 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 510468 ***