[Bug 287625] New: ItemDeleteJob error, causing akonadi<-->akonadi_mixedmaildir_resource communication to stall

[Ahti Heinla]

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

           Summary: ItemDeleteJob error, causing
                    akonadi<-->akonadi_mixedmaildir_resource communication
                    to stall
           Product: kdepim
           Version: 4.7
          Platform: Fedora RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: libkdepim
        AssignedTo: kdepim-bugs at kde.org
        ReportedBy: ahti at ahti.bluemoon.ee


Version:           4.7 (using KDE 4.7.3) 
OS:                Linux

Akonadi::ItemDeleteJob constructors expect to get either a *non-empty* list of
items to be deleted, or a valid collection to be deleted; it does not tolerate
an *empty* list of items to be deleted. However,
RetrieveItemsJob::Private::storeListResult() in akonadi_mixedmaildir_resource
sometimes gives it just that: an empty mServerItemsByRemoteId.values() list.
This causes ItemDeleteJob to report error "Invalid collection specified", and
Akonadi<-->akonadi_mixedmaildir_resource communication stalls (akonadiconsole
debugger shows a transaction BEGIN followed by nothing), and this in turn
causes all kinds of major problems in KMail (KMail becomes out of sync with
akonadi_mixedmaildir_resource, cannot even open e-mail messages).

Reproducible: Sometimes

Steps to Reproduce:
1. akonadictl start
2. akonadiconsole
3. In akonadiconsole "Browser" tab, click "Synchronize Folder" on any KMail
Folder

Actual Results:  
In akonadiconsole "Agents" tab, status of "KMail Folders" should be
"Synchronizing email folder <XYZ>" for some time, then become "Ready" again

Expected Results:  
In akonadiconsole "Agents" tab, status of "KMail Folders" goes to
"Synchronizing email folder <XYZ>" forever (at least hours, even with an empty
folder)

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.