Bug 104205

Well, maybe it's important to emphasize that only the moving operation will not cause the crash. It's the fact that the target folder is a) remote and b) has a problem with its subfolder. 

Here is the crash log...:

>>>>>>>>>>>

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)

[.... same line all over again...]

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1235419008 (LWP 8120)]
(no debugging symbols found)

[... same line agian and again...]

(no debugging symbols found)
[KCrash handler]
#3  0xb5c6bb49 in KMail::CachedImapJob::slotPutMessageInfoData ()
   from /usr/lib/libkmailprivate.so
#4  0xb5c6e618 in KMail::CachedImapJob::qt_invoke ()
   from /usr/lib/libkmailprivate.so
#5  0xb706571c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#6  0xb7887ec7 in KIO::Job::infoMessage () from /usr/lib/libkio.so.4
#7  0xb78719fa in KIO::SimpleJob::slotInfoMessage () from /usr/lib/libkio.so.4
#8  0xb78887d5 in KIO::SimpleJob::qt_invoke () from /usr/lib/libkio.so.4
#9  0xb7889deb in KIO::TransferJob::qt_invoke () from /usr/lib/libkio.so.4
#10 0xb706571c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb7065bbd in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#12 0xb7866bc7 in KIO::SlaveInterface::infoMessage ()
   from /usr/lib/libkio.so.4
#13 0xb7864977 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4
#14 0xb78642a9 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4
#15 0xb7861cdb in KIO::Slave::gotInput () from /usr/lib/libkio.so.4
#16 0xb78639f8 in KIO::Slave::qt_invoke () from /usr/lib/libkio.so.4
#17 0xb706571c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#18 0xb706587d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#19 0xb73a5452 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#20 0xb7081f00 in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#21 0xb7008e1f in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#22 0xb700841e in QApplication::notify () from /usr/lib/libqt-mt.so.3
#23 0xb75bbac5 in KApplication::notify () from /usr/lib/libkdecore.so.4
#24 0xb6ff881a in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/libqt-mt.so.3
#25 0xb6fb1cb3 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#26 0xb701b1d8 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#27 0xb701b088 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#28 0xb7009071 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#29 0x08058aeb in ?? ()
#30 0xbffff9b0 in ?? ()
#31 0x00000001 in ?? ()
#32 0x00000001 in ?? ()
#33 0x00000000 in ?? ()
#34 0x00000000 in ?? ()
#35 0x00000001 in ?? ()
#36 0x08066220 in _IO_stdin_used ()
#37 0x00000000 in ?? ()
#38 0x08065651 in _IO_stdin_used ()
#39 0x0806563d in _IO_stdin_used ()
#40 0xbffff9d8 in ?? ()
#41 0x412e76be in operator new () from /usr/lib/libstdc++.so.5
#42 0x4102e904 in __libc_start_main () from /lib/tls/libc.so.6
#43 0x08058211 in ?? ()
<<<<<<<<<<<

Notice:

I have found out that this is only the case when a folder cannot be set up 
correctly on the imap server. Though, this leads to a crash on the client 
side. 

All this is on a disconnected imap account? What is the exact error message on syncing?

> All this is on a disconnected imap account? What is the exact error message
> on syncing?

Hi Till,
I think that the folder was not created on the kolab box (only in the cache in 
kmail). I was able to move the email into the kmail cache, but then the whole 
kontact crashed without an error message. The next time I started it up, 
again, the email was in the according folder. Presumably yet still in the 
cache, but not on the kolab server. Please note that I did the following: 
Move the folder contents back on the local storage, delete the cached folder, 
create it again, move the whole stuff onto kolab again. Now it works without 
any error / crash.
Obviously there is a potential crash when the cache is not synced with the 
imap server, i.e. when the folder does not exist on the imap server and the 
user tries to move data into the subfolder. - Regards, Markus

*** This bug has been marked as a duplicate of 97274 ***