GNOME Bugzilla – Bug 482860
crash in Tasks: sending email
Last modified: 2008-03-27 15:03:31 UTC
What were you doing when the application crashed? sending email Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 124788736 vsize: 124788736 resident: 31449088 share: 20955136 rss: 31449088 rss_rlim: 4294967295 CPU usage: start_time: 1191396676 rtime: 214 utime: 193 stime: 21 cutime:0 cstime: 0 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 -1208936736 (LWP 4323)] [New Thread -1250661488 (LWP 4373)] [New Thread -1211036784 (LWP 4343)] [New Thread -1271719024 (LWP 4341)] [New Thread -1261229168 (LWP 4334)] [New Thread -1239778416 (LWP 4331)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 167335
Thread 1 (Thread -1208936736 (LWP 4323))
----------- .xsession-errors --------------------- (evolution:4323): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkEntry' (evolution:4323): Gtk-CRITICAL **: gtk_entry_get_text: assertion `GTK_IS_ENTRY (entry)' failed (evolution:4323): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkEditable' (evolution:4323): Gtk-CRITICAL **: gtk_editable_get_position: assertion `GTK_IS_EDITABLE (editable)' failed X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1400978 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 160 Minor opcode: 6 Resource id: 0x1a5 --------------------------------------------------
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 447591 ***