GNOME Bugzilla – Bug 473489
crash in Tasks: trying to download my em...
Last modified: 2007-09-24 16:41:38 UTC
What were you doing when the application crashed? trying to download my email. Unsure of what caused it, but I do have gkrellm installed and running; but WITHOUT the 'email' plugin installed. This is the 5th or 6th time it has crashed. 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.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 669585408 vsize: 669585408 resident: 39907328 share: 16822272 rss: 39907328 rss_rlim: 18446744073709551615 CPU usage: start_time: 1188896674 rtime: 335 utime: 266 stime: 69 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496418400 (LWP 3445)] [New Thread 1136679248 (LWP 3468)] [New Thread 1126189392 (LWP 3467)] [New Thread 1105209680 (LWP 3462)] [New Thread 1084229968 (LWP 3458)] (no debugging symbols found) 0x000000317000d89f in waitpid () from /lib64/libpthread.so.0
+ Trace 160329
Thread 5 (Thread 1084229968 (LWP 3458))
----------- .xsession-errors --------------------- (evolution:3445): camel-WARNING **: Could not find key entry for word '00000000': Success (evolution:3445): camel-WARNING **: Could not find key entry for word '0x00000000': Success (evolution:3445): camel-WARNING **: Could not find key entry for word '00000000': Success (evolution:3445): camel-WARNING **: Could not find key entry for word '0x00000000': Success (evolution:3445): camel-WARNING **: Could not find key entry for word '2fidusper85434220070818': Success --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find *** This bug has been marked as a duplicate of 470267 ***
*** Bug 473490 has been marked as a duplicate of this bug. ***
*** Bug 474212 has been marked as a duplicate of this bug. ***