GNOME Bugzilla – Bug 495973
crash in File Browser:
Last modified: 2007-11-13 12:12:15 UTC
Version: 2.18.3 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Amaranth Icon Theme: Amaranth Memory status: size: 79130624 vsize: 79130624 resident: 31105024 share: 15835136 rss: 31105024 rss_rlim: 4294967295 CPU usage: start_time: 1194810536 rtime: 2266 utime: 1958 stime: 308 cutime:414 cstime: 17 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 -1227322752 (LWP 8320)] (no debugging symbols found) 0xb7eee7f2 in ?? () from /lib/ld-linux.so.2
+ Trace 177087
Thread 1 (Thread -1227322752 (LWP 8320))
----------- .xsession-errors --------------------- ** Message: volume = 0 /usr/share/themes/Amaranth/gtk-2.0/gtkrc:1: No se ha podido encontrar el archivo «include»: «iconrc» JACK tmpdir identified as [/dev/shm] /usr/share/themes/Amaranth/gtk-2.0/gtkrc:1: No se ha podido encontrar el archivo «include»: «iconrc» ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** ERROR **: file fm-tree-model.c: line 1531 (fm_tree_model_unref_node): assertion failed: (node->ref_count > 0) aborting... /usr/share/themes/Amaranth/gtk-2.0/gtkrc:1: No se ha podido encontrar el archivo «include»: «iconrc» /usr/share/themes/Amaranth/gtk-2.0/gtkrc:1: No se ha podido encontrar el archivo «include»: «iconrc» --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 461139 ***