[Bug 259798] Assert in IMAP resource ("!set.toImapSequenceSet().trimmed().isEmpty()") [KIMAP::FetchJob::setSequenceSet, RetrieveItemTask::triggerFetchJob, RetrieveItemTask::onSelectDone]

[Kevin Ottens]

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


Kevin Ottens <ervin at kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDSINFO
         Resolution|                            |WAITINGFORINFO




--- Comment #6 from Kevin Ottens <ervin kde org>  2011-09-17 16:53:51 ---
To debug that kind of cases efficiently, I'd need to be provided with some idea
of the IMAP traffic which created the issue. That can be done by setting the
KIMAP_LOGFILE environment variable and restarting the akonadiserver.

For instance:
export KIMAP_LOGFILE=imaplog
akonadictl restart

Look at the pid of the imap resource you should then have a couple of
imaplog.pid.* files. Wait for the crash, and then provide me what happened
before the crash. It's the best way for me to create a test case that I can
reproduce here. Only caveat though is that some private data is likely in the
log (except the authentication phase, after that it logs everything) so you'd
have to trust me with your data and send it privately.

Also I would need some more information of the structure of the conflicting
messages on the akonadi side, using akonadiconsole perhaps?

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