GNOME Bugzilla – Bug 514311
crash in Tasks: send/receive email.....
Last modified: 2008-02-04 17:26:00 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: 186716160 vsize: 186716160 resident: 54865920 share: 37830656 rss: 54865920 rss_rlim: 4294967295 CPU usage: start_time: 1202137551 rtime: 802 utime: 656 stime: 146 cutime:0 cstime: 2 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 -1208797472 (LWP 17910)] [New Thread -1309029488 (LWP 18005)] [New Thread -1210897520 (LWP 18004)] [New Thread -1277166704 (LWP 17978)] [New Thread -1298539632 (LWP 17948)] [New Thread -1256186992 (LWP 17945)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 188052
Thread 1 (Thread -1208797472 (LWP 17910))
----------- .xsession-errors (48391 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 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 364700 ***