GNOME Bugzilla – Bug 496936
crash in File Browser:
Last modified: 2007-11-15 09:26:22 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.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 88739840 vsize: 88739840 resident: 29659136 share: 15855616 rss: 29659136 rss_rlim: 4294967295 CPU usage: start_time: 1195087463 rtime: 2019 utime: 1885 stime: 134 cutime:66 cstime: 11 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 0xb6e006b0 (LWP 3993)] (no debugging symbols found) 0xb7650bf1 in waitpid () from /lib/libpthread.so.0
+ Trace 177791
Thread 1 (Thread 0xb6e006b0 (LWP 3993))
----------- .xsession-errors (8 sec old) --------------------- ** 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 ** Message: Failed to write /home/juan/Desktop/wwwhidro/hc/ttm.gif to thumbnail pixbuf loader: El cargador de imágenes GIF no puede entender esta imagen. ** Message: Failed to write /home/juan/Desktop/wwwhidro/hc/ttm.gif to thumbnail pixbuf loader: El cargador de imágenes GIF no puede entender esta imagen. 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... --------------------------------------------------
Thanks for taking the time to report this. This bug has been fixed in GNOME. Please report this problem to http://bugs.debian.org instead in order to get this fixed. Thanks! *** This bug has been marked as a duplicate of 440988 ***