GNOME Bugzilla – Bug 553889
crash in File Browser: estaba instalando alguno...
Last modified: 2008-09-26 17:17:23 UTC
Version: 2.20.0 What were you doing when the application crashed? estaba instalando algunos paquetes para wine luego cerre 2 ventanas del navegador. Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-amd64 #1 SMP Wed Sep 10 15:31:12 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 476205056 vsize: 476205056 resident: 46448640 share: 18747392 rss: 46448640 rss_rlim: 18446744073709551615 CPU usage: start_time: 1222402106 rtime: 1428 utime: 1254 stime: 174 cutime:47 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 0x7f7545acc780 (LWP 3249)] 0x00007f7540abd5ff in waitpid () from /lib/libpthread.so.0
+ Trace 207372
Thread 1 (Thread 0x7f7545acc780 (LWP 3249))
----------- .xsession-errors --------------------- (npviewer.bin:7447): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: wrong ELF class: ELFCLASS64 (npviewer.bin:7447): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: wrong ELF class: ELFCLASS64 (npviewer.bin:7447): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: wrong ELF class: ELFCLASS64 (npviewer.bin:7447): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: wrong ELF class: ELFCLASS64 (gnome-terminal:7488): GnomeUI-WARNING **: While connecting to session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed. (nautilus:3249): Gtk-CRITICAL **: _gtk_rbtree_reorder: assertion `tree->root->count == length' failed ** ** ERROR:(fm-tree-model.c:1531):fm_tree_model_unref_node: assertion failed: (node->ref_count > 0) --------------------------------------------------
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 ***