[Bug 272920] Odd sync issues when deleting mail

[Richard Van Den Boom]

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


Richard Van Den Boom <richard.vdboom at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |richard.vdboom at gmail.com




--- Comment #2 from Richard Van Den Boom <richard vdboom gmail com>  2011-06-07 07:08:00 ---
I have a very similar issue, but not with IMAP, with POP.
One of my mail folder contains about 5930 mails, retrieved using POP. It was
upgraded to akonadi when I upgraded to KMail 2.0.95 and worked well.
Yesterday, the Conflict box appeared for no apparent reason (I wanted to move
some files to the Trash). I dismissed it and now, I get a "Given item
identifier is empty" when I try to get to that folder, with messages like the
following appearing on the command line if KMail is started in a console :

db at coyote:~$ kmail
kmail2(2948)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
kmail2(2948)/kdeui (kdelibs): Attempt to use QAction "" with KXMLGUIFactory! 
vdb at coyote:~$ kmail2(2948)/libakonadi
Akonadi::EntityTreeModelPrivate::fetchJobDone: Job error:  "Erreur inconnue.
(Unable to fetch item from backend)" 

kmail2(2948)/libakonadi Akonadi::EntityTreeModelPrivate::monitoredItemChanged:
Got a stale notification for an item which was already removed. 3417
"1198005228.3081.YsBA5:2,S" 
kmail2(2948)/libakonadi Akonadi::EntityTreeModelPrivate::monitoredItemChanged:
Got a stale notification for an item which was already removed. 3422
"1198582054.2938.OwDbt:2,S" 
kmail2(2948)/libakonadi Akonadi::EntityTreeModelPrivate::monitoredItemChanged:
Got a stale notification for an item which was already removed. 3432
"1199401979.29684.hXvzP:2,S" 

The main issue is that Kmail do not display the folder contents anymore,
meaning I lost access to 5 years of mails.

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