GNOME Bugzilla – Bug 500418
crash in Tasks: estava lendo a lista de ...
Last modified: 2007-11-29 14:32:54 UTC
Version: 2.10 What were you doing when the application crashed? estava lendo a lista de e-mails da caixa de entrada e travou, estava em 47% please sendme spanish language. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 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: 159969280 vsize: 159969280 resident: 69812224 share: 29413376 rss: 69812224 rss_rlim: 4294967295 CPU usage: start_time: 1196351555 rtime: 12667 utime: 7910 stime: 4757 cutime:45 cstime: 22 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 -1208981792 (LWP 3119)] [New Thread -1294623856 (LWP 3168)] [New Thread -1284134000 (LWP 3165)] [New Thread -1242166384 (LWP 3139)] [New Thread -1221186672 (LWP 3135)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 180083
Thread 3 (Thread -1284134000 (LWP 3165))
----------- .xsession-errors (6 sec old) --------------------- (evolution:3119): camel-WARNING **: Could not find key entry for word '88p1h890000000000000': Multibyte ou caracter largo inválido (evolution:3119): camel-WARNING **: Could not find key entry for word '88p1my50000000000000': Multibyte ou caracter largo inválido (evolution:3119): camel-WARNING **: Could not find key entry for word '88p1rn00000000000000': Multibyte ou caracter largo inválido (evolution:3119): camel-WARNING **: Could not find key entry for word '88p1h890000000000000': Multibyte ou caracter largo inválido (evolution:3119): e-data-server-WARNING **: Could not open converter for 'unicode-1-1-utf-7' to 'UTF-8' charset --------------------------------------------------
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 339602 ***