On Tue, 2007-10-30 at 14:47 -0500, Chris Boyce wrote: > Just my own suggestions, but I set my "Mark messages as read after..." > option to 0 seconds (immediate), and don't have any problems. > > I'm a Gentoo user as well, and found the constant bug-buddy crashes in > 2.10 unbearable. I decided to switch evolution to the Gentoo test > branch so I could get 2.12, and have been much happier. > > If you're not a Gentoo "genius" (I'm certainly not), just add these > lines to /etc/portage/package.keywords: > > gnome-extra/evolution-data-server ~x86 > gnome-extra/evolution-exchange ~x86 > mail-client/evolution ~x86 > gnome-extra/gtkhtml ~x86 > gnome-extra/evolution-webcal ~x86 > > ...assuming you use the Exchange backend. Then do an emerge to install > it. I'm not a fan of mixing stable & test packages, but this seems safe > enough, since you're only pulling evolution (and gtkhtml) from the > testing branch.
Chris, I'll have to get around to getting the later version. I noticed after creating a filter and applying the filters to a message in my inbox, the cpu went to 100%. That makes me wonder if the message filters are the culprit when checking mail. I have many filters setup. Do you use a lot of filters without any problems in the later version? I set the 'Mark messages as read...' option to 0 as you suggested. Same problem. I did notice that the status bar said 'Formatting message' while the cpu was maxed out. Thanks, Tom _______________________________________________ Evolution-list mailing list Evolution-list@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-list
