Version: SVN trunk (KDE 4) (using Devel) OS: Linux When i change folder (abd this happens when i changed to the folders i created and not the kmail default folders), it outputs this kind of message: Unkown error. (NO [LRCONFLICT] Resource tries to modify item with dirty payload, aborting STORE. ) I really dont get what this error message means??? And why the hell it outputs always this message when i click in one of the folders that were created by me? Reproducible: Always OS: Linux (x86_64) release 2.6.33.5-desktop-2mnb Compiler: gcc
Hej, can you still reproduce with current version (4.6beta)? I think we should have fixed most of these conflict issues now. Ciao, Tobias
I'm seeing this in the 4.8.1 Kubuntu update. Everything was working prior to the update. Since then my Kmail Folders resource is displaying the error message (NO[LRCONFLICT} Resource tries to modify item with dirty payload, aborting STORE.) Only is failing with this specific resource. Others are working as expected..
Encountered the same problem on fedora update to kde 4.8.1 I was able to resolve the problem by going through the following steps: 1. Open Akonadi console, 2. Right click on faulty resource (in my case "KMail Folders") and select "Clone Agent." 3. A new reource with the same name should appear except with "(Clone)" next to the name (In my case "KMail Folders (Clone)"). 4. Turn off faulty resource by right clicking the resource and selecting "Toggle Online/Offline." 5. Open Kmail or Kontact and ensure that all your email shows up in the cloned resource (In my case I had to click on each folder in the cloned resource before my email actually appeared in the folder). While carrying out this step, I noticed that the faulty resource was turned on again, but I simply switched to the Akonadiconsole window and repeating step 4. 6. Once all your email appeares in the cloned resource, closed Kmail, switch back to the Akonadi console window, and delete the faulty resource by selecting it and clicking "Remove." 7. If you so choose, you may rename the cloned resource by deleting the "(Cloned)" in front of it. 8. After step 7 go through all your account, Identities, and filter settings to make sure that all the settings are configured to use the new cloned resource. Hope this helps
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!