GNOME Bugzilla – Bug 496107
crash in Tasks: I don'ŧ know -- Evolutio...
Last modified: 2007-12-04 16:59:49 UTC
Version: 2.12 What were you doing when the application crashed? I don'ŧ know -- Evolution was in the background, and Tasks module was not even opened. Distribution: Fedora release 8 (Werewolf) Gnome Release: 2.20.1 2007-10-15 (Red Hat, Inc) BugBuddy Version: 2.20.1 System: Linux 2.6.23.1-42.fc8 #1 SMP Tue Oct 30 13:18:33 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 741462016 vsize: 741462016 resident: 88985600 share: 22605824 rss: 88985600 rss_rlim: 18446744073709551615 CPU usage: start_time: 1194855905 rtime: 7895 utime: 6635 stime: 1260 cutime:61 cstime: 128 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 46912496425664 (LWP 23574)] [New Thread 1157658960 (LWP 20785)] [New Thread 1094986064 (LWP 20783)] [New Thread 1084496208 (LWP 20776)] [New Thread 1147169104 (LWP 20772)] [New Thread 1074006352 (LWP 23813)] [New Thread 1115699536 (LWP 23586)] 0x000000323fe0e0bf in waitpid () from /lib64/libpthread.so.0
+ Trace 177174
Thread 2 (Thread 1157658960 (LWP 20785))
----------- .xsession-errors (2458 sec old) --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) get ceplm@seznam.cz pop://ceplm%40seznam.cz@pop3.seznam.cz/ Find Items 0 get ceplm@seznam.cz pop://ceplm%40seznam.cz@pop3.seznam.cz/ Find Items 0 ...Too much output, ignoring rest... --------------------------------------------------
I'd say this is bug 427105 which is NEEDINFO right now. Could you please answer bug 427105 comment 4 ? TIA! *** This bug has been marked as a duplicate of 427105 ***