https://bugs.kde.org/show_bug.cgi?id=297930

--- Comment #10 from [email protected] ---
Hi,
I do not remember all the steps I did before getting a running solution, but 
for sure, at least  on one machine, the cleaning of duplicate was not enough 
(by the way I made a duplicate cleaning on both the systems). So I had to 
manually clean (i.e. delete) some files under the akonadi directory and so, 
after a long while I got a working system.

On next days I will try to upgarde another machine, so if I will face the same 
problem I will be going to apply your solution  in a neat way and I will be 
able to tell you if it is working or not on it.

cheers
Giovanni

Le Lunedi 23 Decembre 2013 16:38:57 tu scribeva:
> https://bugs.kde.org/show_bug.cgi?id=297930
> 
> Marc Bessières <[email protected]> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
> CC|                            |[email protected]
> 
> --- Comment #9 from Marc Bessières <[email protected]> ---
> Hi,
> 
> Yesterday, I upgraded from opensuse 12.3 to 13.1, and kmail(4.11.3) was
> blocked opening messages, using a lot of cpu for kmail, akonadi and mysql.
> Looking for a solution I found this bug report that looked like my issue.
> 
> But the solution to fix my issue was in
> https://bugs.kde.org/show_bug.cgi?id=322958
> 
> I summarize, but you can read the other bug report.
> 
> run akonadiconsole
> in the akonadiconsole tab Browser look for duplicate entries, for me all
> were duplicated (Inbox, Outbox, Templates...) and remove the duplicate
> ones, but only the ones that are empty.
> 
> Then I launched again kmail and it was fine.
> 
> Can you check if this workaround fixes your issue?
> This would mean this bug entry is a duplicate.
> 
> Cheers

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Kdepim-bugs mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kdepim-bugs

Reply via email to