GNOME Bugzilla – Bug 482859
crash in Tasks: sending email
Last modified: 2008-03-27 15:03:07 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: 147472384 vsize: 147472384 resident: 42700800 share: 21643264 rss: 42700800 rss_rlim: 4294967295 CPU usage: start_time: 1191396414 rtime: 1320 utime: 1183 stime: 137 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 -1208867104 (LWP 4204)] [New Thread -1240130672 (LWP 4307)] [New Thread -1250620528 (LWP 4293)] [New Thread -1300595824 (LWP 4259)] [New Thread -1311085680 (LWP 4231)] [New Thread -1261110384 (LWP 4218)] [New Thread -1210967152 (LWP 4213)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 167334
Thread 1 (Thread -1208867104 (LWP 4204))
----------- .xsession-errors --------------------- Major opcode: 54 Minor opcode: 0 Resource id: 0x140078d (evolution:4204): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkEntry' (evolution:4204): Gtk-CRITICAL **: gtk_entry_get_text: assertion `GTK_IS_ENTRY (entry)' failed (evolution:4204): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkEditable' (evolution:4204): Gtk-CRITICAL **: gtk_editable_get_position: assertion `GTK_IS_EDITABLE (editable)' failed 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 ***