https://bugs.kde.org/show_bug.cgi?id=312460
--- Comment #55 from Christian Mollekopf <mollek...@kolabsys.com> --- Thanks for the responses so far. Here's another test I'd need the results from: * wait for the bug to appear * close or at least don't use other akonadi apps than kmail * fire up akonadiconsole ** go to "Notification Monitor", rightclick and check "Enabled" ** go to "Debugger" and check "Enable Debugger" on the top left * If possible, use webmail to send an email to your account so it will end up in the affected folder. Avoid using KMail or any other akonadi apps to not clutter the logs. ** If this is not possible, move an email using webmail (preferred) or kmail to the affected folder. * copy the content of the Debugger "KMail Kernel ETM" tab, and make a screenshot of the "Notification Monitor" with all items expanded. * Double check that the email was actually affected by the bug and note the item id (by checking the item in akonadiconsole). We're looking for: * An "Add" notification in the notification monitor signaling that the sent email has been added to akonadi. ** This ensures the akonadi server properly notified about the email being added. * A "UID FETCH $ITEMID" in the debugger tab ** If this is present, the Akonadi::Monitor properly received the notification and fetched the payload (narrowing the error down to notification delivery from monitor to etm or ETM notification processing) After that I'll have to start posting patches with debug messages I think. Thanks for your help! -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs