GNOME Bugzilla – Bug 506768
crash in File Browser: haciendo click a las pro...
Last modified: 2008-01-02 20:52:45 UTC
Version: 2.18.3 What were you doing when the application crashed? haciendo click a las propiedades de una imagen Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: nuoveXT.2.2 Memory status: size: 152432640 vsize: 152432640 resident: 39231488 share: 17395712 rss: 39231488 rss_rlim: 4294967295 CPU usage: start_time: 1199215040 rtime: 814 utime: 720 stime: 94 cutime:34 cstime: 9 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 0xb6d076b0 (LWP 3641)] [New Thread 0xb23d1b90 (LWP 12742)] [New Thread 0xb2bd2b90 (LWP 12741)] [New Thread 0xb3bd4b90 (LWP 12740)] [New Thread 0xb33d3b90 (LWP 12739)] [New Thread 0xb6483b90 (LWP 12738)] [New Thread 0xb5c82b90 (LWP 12737)] (no debugging symbols found) 0xb7f7c410 in ?? ()
+ Trace 183749
----------- .xsession-errors --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 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 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 440988 ***