GNOME Bugzilla – Bug 561552
crash in Evolution Mail and Calendar: Editing a task
Last modified: 2008-11-19 18:47:56 UTC
What were you doing when the application crashed? Editing a task Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-d820 #1 SMP PREEMPT Fri Oct 31 15:33:43 CET 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 99221504 vsize: 99221504 resident: 26681344 share: 19394560 rss: 26681344 rss_rlim: 4294967295 CPU usage: start_time: 1227115294 rtime: 233 utime: 212 stime: 21 cutime:3 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb65b06d0 (LWP 766)] [New Thread 0xb27b3b90 (LWP 905)] [New Thread 0xb2fb4b90 (LWP 903)] [New Thread 0xb37b5b90 (LWP 884)] 0xb7f1f424 in __kernel_vsyscall ()
+ Trace 210013
Thread 1 (Thread 0xb65b06d0 (LWP 766))
----------- .xsession-errors (35313 sec old) --------------------- Error (350874): Illegal character <3c> in hex string Error (350874): Illegal character <2f> in hex string Error (350874): Illegal character <50> in hex string Error (350874): Illegal character <72> in hex string Error (350874): Illegal character <69> in hex string Error (350874): Illegal character <74> in hex string Error (350874): Illegal character <6f> in hex string Error (350874): Illegal character <72> in hex string Error (350874): Illegal character <2f> in hex string Error (350874): Illegal character <6f> in hex string Error (350874): Illegal character <6c> in hex string Error (350874): Illegal character <75> in hex string Error (350874): Illegal character <6d> in hex string Error (350874): Illegal charact ...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 544187 ***