GNOME Bugzilla – Bug 505366
crash in Tasks:
Last modified: 2007-12-24 16:51:29 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 121503744 vsize: 121503744 resident: 36462592 share: 29884416 rss: 36462592 rss_rlim: 4294967295 CPU usage: start_time: 1198478668 rtime: 60 utime: 53 stime: 7 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 -1208338720 (LWP 13980)] [New Thread -1234175088 (LWP 14005)] [New Thread -1244664944 (LWP 14001)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 182877
Thread 1 (Thread -1208338720 (LWP 13980))
----------- .xsession-errors (933630 sec old) --------------------- (evince:26458): Gdk-CRITICAL **: gdk_draw_pixbuf: assertion `GDK_IS_PIXBUF (pixbuf)' failed (evince:26458): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (evince:26458): GdkPixbuf-CRITICAL **: gdk_pixbuf_new: assertion `width > 0' failed (evince:26458): GdkPixbuf-CRITICAL **: gdk_pixbuf_fill: assertion `GDK_IS_PIXBUF (pixbuf)' failed (evince:26458): Gdk-CRITICAL **: gdk_draw_pixbuf: assertion `GDK_IS_PIXBUF (pixbuf)' failed (evince:26458): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (evince:26458): GdkPixbuf-CRITICAL **: gdk_pixbuf_new: assertion `width > 0' failed ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 431459 ***