rrumberger at web.de
Mon Mar 15 00:12:00 UTC 2010
On Sunday 14 March 2010, lanzen wrote:
> On Saturday 13 March 2010 00:18:31 Reinhold Rumberger wrote:
> > That's a known bug and it won't go away until KMail fully
> > switches to Akonadi, IIRC.
> > https://bugs.kde.org/show_bug.cgi?id=41514
> > As you can see, the report is quite old...
> Thank you Reinhold, very interesting.
> I have noticed we have the same version of KMail, kernel and kde:
> KMail/1.13.1 (Linux/2.6.31-20-generic; KDE/4.4.1; i686;
> Are you affected by this bug as well?
I am and have been for years. I guess everybody is since kmail
doesn't do proper threading when filtering and fetching email. That
just usually doesn't take that much time. I only started noticing it
when I started using spamassassin. (It's nice when you try to write
an email and kmail starts filtering 20-30 emails. Gives one a chance
to relax and do other stuff... ;-) ) What I find most annoying is
that kmail isn't utilising both my CPU cores, so this takes longer
than it needs to.
I don't email a lot, so it isn't too bad for me (4/5 emails I write
go to this list...).
> The funny thing is I've been using kmail - and kontact - for many
> years now and I've never noticed this bug until now exactly from
> the moment when akonaki is started to take over. :D
Lucky you! ;-)
It's been there for most if not all of KDE 3, and it was *really*
annoying back when kmail was still pretty unstable. Chances were, if
you typed anything while kmail was doing its stuff, you'd get a
crash. OTOH, kmail has one of the best crash recovery strategies I've
seen in email programs, so there definitely is a silver lining... :-)
I've only been using kontact on and off because if one of it's
"plugins" keeps crashing, it pulls down all the others, resulting in
quite a bit of lost work (knode is particularly bad as it only saves
its state when it's exiting, making it a virtual certainty that
information is lost).
More information about the kubuntu-users