GNOME Bugzilla – Bug 495610
crash in Open Folder: right clicked icon and s...
Last modified: 2007-11-11 16:48:44 UTC
Version: 2.18.3 What were you doing when the application crashed? right clicked icon and selected properties then this bug buddy came up. Distribution: Debian 4.0 Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.19 #7 SMP PREEMPT Sun Dec 17 22:01:07 CET 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 70246400 vsize: 70246400 resident: 22298624 share: 14221312 rss: 22298624 rss_rlim: 4294967295 CPU usage: start_time: 1194707504 rtime: 3996 utime: 3802 stime: 194 cutime:290 cstime: 38 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1227614544 (LWP 22173)] (no debugging symbols found) 0xb765abf1 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 176811
Thread 1 (Thread -1227614544 (LWP 22173))
----------- .xsession-errors --------------------- (gnome-background-properties:22239): background-properties-WARNING **: Unknown Tag: comment /usr/share/themes/Glossy/gtk-2.0/gtkrc:62: error: unexpected identifier `colorize_scrollbar', expected character `}' /usr/share/themes/Glossy/gtk-2.0/gtkrc:62: error: unexpected identifier `colorize_scrollbar', expected character `}' (gnome-background-properties:22337): background-properties-WARNING **: Unknown Tag: comment (gnome-background-properties:22337): background-properties-WARNING **: Unknown Tag: comment Gtk-ERROR **: file /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store)) aborting... Failed to read a valid object file image from memory. --------------------------------------------------
Thanks for the bug report. This particular bug has been fixed already. Please update. *** This bug has been marked as a duplicate of 440988 ***