On Friday 26 February 2010 05:52:41 Dave Stevens wrote:
A couple of days ago I was using my F11 gnome system where I use
kmail
as pop client and ran some ordinary updates (including several kde
updates) from the usual Fedora repo. Subsequently I got progressively
slower and slower kmail and then my whole system bogged.
The current situation is that kmail is totally unusable, and as soon
as I fire it up my whole system is on the verge of unusability.
My mail is tied up in kmail boxes that I now cannot access. I of
course have work in progress that I can't get at.
There was a pretty good thread on this topic on the fedora-list and it
was suggested that people on this list might have more info.
So what I think is happening is that somehow akonadi and/or nepomuk
are fried, giving extremely slow (glacial) performance for programs
that depend on them. I was able to see from a nepomuk failure message
a link to a kde site where there were instructions for a workaround.
This helped a bit and I will no doubt need to find those instructions
again and get familiar with the process, because the fix is transient.
For unrelated reasons I've had to reboot and every time I do I'm back
in glacial terrain.
Can anyone (PLEASE) suggest a decent fix or provide more information
about this issue?
First, yesterday I posted a message entitled "More nepomuk/kmail problems and
workarounds" - did you read that? I'm happy to report, though, that the non-
starting of kontact was cleared yesterday after an update, although it's not
obvious which updated package cleared the blockage.
The page that has all the issues I've seen so far, and the workarounds (not
sure whether I added yesterday's yet) would be
http://userbase.kde.org/Akonadi
Anne
--
KDE Community Working Group
New to KDE Software? - get help from
http://userbase.kde.org