| Summary: | When I open kmail, and click on a mail, I get the message "the content of the directory is being loaded" | ||
|---|---|---|---|
| Product: | [Applications] kmail2 | Reporter: | Theresa <rockprinzess> |
| Component: | message list | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | critical | CC: | cfeck, dozab2000, marc_bessieres, marian.trenkwalder, Martin, rafaelalcantaraperez, thomas.heidemann |
| Priority: | NOR | Keywords: | triaged |
| Version: | 4.11.1 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Theresa
2013-09-08 19:05:28 UTC
just migrate from gnome to kde on opensuse 12.3 and have the same problem just upgraded my openSUSE (12.2) from KDE 4.10 to 4.11 (openSUSE repository) and have the same problem. MySQL and akonadi server are running on high CPU load. Any news on this? It's frustrating me that I can't use kmail anymore, it's really critical to me and I would hate to switch to another client. Please fix this, as others have confirmed/reported the same behaviour! Thanks!! The same is happening to me and my fellows. I'm using KDE 4.11.2 (in Kubuntu, kdepim version 4:4.11.2-0ubuntu1). Has anybody found a fix for this annoying bug? Thanks! I have the same problem with version 4.11.3 I have fixed it (at least for me) by stopping Kmail/Kontact and so, and then stopping Akonadi: $ akonadictl stop Then, I have renamed ~/.local/share/akonadi: $ mv ~/.local/share/akonadi ~/.local/share/akonadi-old Finally, I started all again and now it works. > I have fixed it (at least for me) by stopping Kmail/Kontact and so, and then
> stopping Akonadi:
> $ akonadictl stop
> Then, I have renamed ~/.local/share/akonadi:
> $ mv ~/.local/share/akonadi ~/.local/share/akonadi-old
> Finally, I started all again and now it works.
That fixed also my Problem.
Hi, Yesterday, I upgraded from opensuse 12.3 to 13.1, and kmail(4.11.3) was blocked opening messages with similar messages about the message being loaded. The system was 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 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 I reconfigured my system to get the bug again and tried the second solution. In my "Local Ordner" there where duplicate Folders. After deletion of that it is no also fixed. Hello! This appears still be related to a version of KMail which uses Nepomuk. Can you reproduce this issue with KMail 4.14 which uses Baloo for mail indexing and Akonadi 1.13? If so, please try to provide a description on how to reproduce it – I know, it may happen randomly, so if its not possible, skip that, but try to find a pattern – and also include details on your setup, whether you use IMAP, POP + Maildir, how many accounts you have and how big they are. As this bug has last changed more than year ago, I will close it in one month in case I do not receive any response that it is still happening. Thank you for reporting the bug and for your further feedback. Setting to waiting for information after I received bugzilla rights to do that. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |