Version: 1.8 (using KDE 3.3.2, (3.1)) Compiler: gcc version 3.3.5 (Debian 1:3.3.5-8) OS: Linux (i686) release 2.4.27-20041122 Steps to reproduce: - delete a thread in a mailbox - switch to an other mailbox - press ctrl-z to undo that deletion environment: online imap, not only in inbox, only happens when deleting a thread, cvs head of approx. last friday with kde 3.3 base. 10% chance this is caused by a bad installation. Trace: sing host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 17643)] [KCrash handler] #5 0x00000000 in ?? () #6 0x42a6a4b4 in KMFolderImap::addMsgQuiet (this=0x84f7208, msgList= {<QGList> = {<> = {<No data fields>}, firstNode = 0x83520b0, lastNode = 0x83520b0, curNode = 0x83520b0, curIndex = 0, numNodes = 1, iterators = 0x0}, <No data fields>}) at /usr/src/kdepim/kmail/kmfolderimap.cpp:321 #7 0x42a733ff in KMFolderImap::qt_invoke (this=0x84f7208, _id=9, _o=0xbfffec30) at kmfolderimap.moc:286 #8 0x416175ac in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #9 0x42b3b178 in KMail::FolderJob::messageCopied (this=0x8ca5738, t0= {<QGList> = {<> = {<No data fields>}, firstNode = 0x8819ea8, lastNode = 0x8819ea8, curNode = 0x8819ea8, curIndex = 0, numNodes = 1, iterators = 0x0}, <No data fields>}) at folderjob.moc:169 #10 0x42b4543b in KMail::ImapJob::slotCopyMessageResult (this=0x8ca5738, job=0x8ebcce0) at /usr/src/kdepim/kmail/imapjob.cpp:631 #11 0x42b45a16 in KMail::ImapJob::qt_invoke (this=0x8ca5738, _id=8, _o=0xbfffed90) at imapjob.moc:132 #12 0x416175ac in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #13 0x40bbf14a in KIO::Job::result () from /usr/lib/libkio.so.4 #14 0x40ba845c in KIO::Job::emitResult () from /usr/lib/libkio.so.4 #15 0x40ba995c in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.4 #16 0x40bbfbcd in KIO::SimpleJob::qt_invoke () from /usr/lib/libkio.so.4 #17 0x416175ac in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #18 0x416173d4 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #19 0x40b9e7ee in KIO::SlaveInterface::finished () from /usr/lib/libkio.so.4 #20 0x40b9d369 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4 #21 0x40b9c889 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4 #22 0x40b9a2bb in KIO::Slave::gotInput () from /usr/lib/libkio.so.4 #23 0x40b9bfd8 in KIO::Slave::qt_invoke () from /usr/lib/libkio.so.4 #24 0x416175ac in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #25 0x4161770d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #26 0x41956092 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3 #27 0x41633d70 in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3 #28 0x415babff in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #29 0x415ba1fe in QApplication::notify () from /usr/lib/libqt-mt.so.3 #30 0x41149e03 in KApplication::notify () from /usr/lib/libkdecore.so.4 #31 0x415aa5fa in QEventLoop::activateSocketNotifiers () from /usr/lib/libqt-mt.so.3 #32 0x41563c23 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #33 0x415ccf58 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #34 0x415cce08 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #35 0x415bae51 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #36 0x0805ad99 in main (argc=1, argv=0xbffffbb4) at /usr/src/kdepim/kontact/src/main.cpp:156
*** Bug 152569 has been marked as a duplicate of this bug. ***
*** Bug 152922 has been marked as a duplicate of this bug. ***
*** Bug 166152 has been marked as a duplicate of this bug. ***
*** Bug 201711 has been marked as a duplicate of this bug. ***
*** Bug 212885 has been marked as a duplicate of this bug. ***
*** Bug 247983 has been marked as a duplicate of this bug. ***
[Comment from a bug triager] From bug 253564: - What I was doing when the application crashed: moving hundreds of messages from one imap folder to another (different mailboxes) Both mail boxes are set up as disconnected IMAP boxes if it is important.
*** Bug 253564 has been marked as a duplicate of this bug. ***
Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding
KMail2 is a complete rewrite in the IMAP stuff. So there's no way this bug could be relevant any longer.