Anyone seeing this error? It started after I upgraded my Fedora 17 to KDEPIM 4.9.5 this morning and then continued after I upgraded to Feodra 18 and KDEPIM/KMail 4.10.1-1. How do I fix this???
I *have* filed a bug report (Bug #317293 on bugs.kde.org) but haven't heard anything back yet....'course it's only been this afternoon, but still...
On Sun, Mar 24, 2013 at 6:35 PM, John Aldrich jmaldrich@yahoo.com wrote:
Anyone seeing this error? It started after I upgraded my Fedora 17 to KDEPIM 4.9.5 this morning and then continued after I upgraded to Feodra 18 and KDEPIM/KMail 4.10.1-1. How do I fix this???
I just did a fresh install of Fedora 18. When I attempted to start KMail the first time, I got the same error.
I *have* filed a bug report (Bug #317293 on bugs.kde.org) but haven't heard anything back yet....'course it's only been this afternoon, but still...
Just added my comment...
Steven P. Ulrick
John Aldrich wrote:
Anyone seeing this error? It started after I upgraded my Fedora 17 to KDEPIM 4.9.5 this morning and then continued after I upgraded to Feodra 18 and KDEPIM/KMail 4.10.1-1. How do I fix this???
In my experience, that error is one of those generic "something real bad happened" bugs/crashes. The path of least resistance may well be to reset akonadi config/accounts(1), and start over.
To reset akonadi...
1. stop akonadi: $ akonadictl stop
2. backup/rename/delete anything matching: ~/.kde/share/config/akonadi* ~/.config/akonadi/ ~/.local/share/akonadi/
3. optionally backup/rename/delete kmail related stuff ~/.kde/share/apps/kmail2/ ~/.kde/share/config/kmail2rc
4. (restart) akonadi: $ akonadictl start