GNOME Bugzilla – Bug 497946
crash in Home Folder: rechstklick->eigenschaft...
Last modified: 2007-11-19 02:12:59 UTC
What were you doing when the application crashed? rechstklick->eigenschaften Distribution: Debian lenny/sid Gnome Release: 2.20.1 2007-10-26 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-2-686-bigmem #1 SMP Fri Aug 31 01:40:59 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: CleanIce-Debian Icon Theme: Amaranth Memory status: size: 80560128 vsize: 80560128 resident: 22589440 share: 14540800 rss: 22589440 rss_rlim: 4294967295 CPU usage: start_time: 1195404913 rtime: 554 utime: 522 stime: 32 cutime:0 cstime: 0 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 0xb6cad8c0 (LWP 28047)] (no debugging symbols found) 0xb75cabf1 in waitpid () from /lib/libpthread.so.0
+ Trace 178543
Thread 1 (Thread 0xb6cad8c0 (LWP 28047))
----------- .xsession-errors --------------------- ** Message: drive = 0 ** Message: volume = 0 (nautilus:28047): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_height > 0' failed (nautilus:28047): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (nautilus:28047): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (nautilus:28047): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_height > 0' failed (nautilus:28047): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed 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... --------------------------------------------------
This is a Debian specific problem, and not an upstream GNOME issue. The Debian team is working on a fix. *** This bug has been marked as a duplicate of 440988 ***