GNOME Bugzilla – Bug 514320
crash in Tasks: send/receive email
Last modified: 2008-02-26 23:35:34 UTC
Version: 2.10 What were you doing when the application crashed? send/receive email 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.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 188280832 vsize: 188280832 resident: 69910528 share: 38141952 rss: 69910528 rss_rlim: 4294967295 CPU usage: start_time: 1202137886 rtime: 2214 utime: 1773 stime: 441 cutime:60 cstime: 15 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 -1209239840 (LWP 18099)] [New Thread -1288701040 (LWP 18273)] [New Thread -1232737392 (LWP 18247)] [New Thread -1221829744 (LWP 18237)] [New Thread -1278211184 (LWP 18137)] [New Thread -1257231472 (LWP 18136)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 188056
Thread 2 (Thread -1288701040 (LWP 18273))
----------- .xsession-errors (49311 sec old) --------------------- (mail-notification:3282): mail-notification-WARNING **: daved@exchange.hilgraeve.com: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found (mail-notification:3282): mail-notification-WARNING **: daved@exchange.hilgraeve.com: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found (mail-notification:3282): mail-notification-WARNING **: daved@exchange.hilgraeve.com: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found (mail-notification:3282): mail-notification-WARNING **: daved@exchange.hilgraeve.com: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found (mail-notification:3282): mail-notification-WARNING **: daved@exchange.hilgraeve.com: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found (mail-notification:3282): mail-notification-WARNING **: daved@exchange.hilgraeve.com: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found (mail-notification:3282): mail-notification-WARNING **: daved@exchange.hilgraeve.com: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found ...Too much output, ignoring rest... --------------------------------------------------
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 499975 ***