Version: 1.8 (using KDE 3.4.0, compiled sources) Compiler: gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-49) OS: Linux (i686) release 2.4.21-27.0.1.EL-MI_20050124 KMail crashes when I delete mail in my Inbox (which resides in an IMAP account). The bug is reproducable, actually, I currently have no way of deleting ANY mail, which is really bad, as I use kmail for my daily work. I attach a backtrace below: Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1218617216 (LWP 11872)] [KCrash handler] #3 0x01ad13ee in QGDict::look_string (this=0xa3aee10, key=@0xbfff7710, d=0x0, op=0) at tools/qgdict.cpp:332 #4 0x01f0c78c in QDict<KMail::SortCacheItem>::operator[] (this=0xa3aee10, k=@0xbfff7710) at qdict.h:73 #5 0x01f014d7 in KMHeaders::msgRemoved (this=0xa3aed38, id=49, msgId= {static null = {static null = <same as static member of an already seen type>, d = 0x9e7e050, static shared_null = 0x9e7e050}, d = 0xa357eb8, static shared_null = 0x9e7e050}) at kmheaders.cpp:1000 #6 0x01f0b83f in KMHeaders::qt_invoke (this=0xa3aed38, _id=112, _o=0xbfff77a0) at kmheaders.moc:299 #7 0x017e5765 in QObject::activate_signal (this=0xa301838, clist=0xa59ad40, o=0xbfff77a0) at kernel/qobject.cpp:2355 #8 0x01f428d1 in KMFolder::msgRemoved (this=0xa301838, t0=49, t1= {static null = {static null = <same as static member of an already seen type>, d = 0x9e7e050, static shared_null = 0x9e7e050}, d = 0xa357eb8, static shared_null = 0x9e7e050}) at kmfolder.moc:247 #9 0x01f432b6 in KMFolder::qt_emit (this=0xa301838, _id=9, _o=0xbfff78b0) at kmfolder.moc:367 #10 0x017e573c in QObject::activate_signal (this=0xa301978, clist=0xa3021f0, o=0xbfff78b0) at kernel/qobject.cpp:2353 #11 0x01f5ce17 in FolderStorage::msgRemoved (this=0xa301978, t0=49, t1= {static null = {static null = <same as static member of an already seen type>, d = 0x9e7e050, static shared_null = 0x9e7e050}, d = 0xa357eb8, static shared_null = 0x9e7e050}) at folderstorage.moc:281 #12 0x01f59cac in FolderStorage::take (this=0xa301978, idx=49) at folderstorage.cpp:398 #13 0x01fd39c9 in KMFolderImap::take (this=0xa301978, idx=49) at kmfolderimap.cpp:539 #14 0x01f40908 in KMFolder::take (this=0xa301838, idx=49) at kmfolder.cpp:319 #15 0x01fee421 in KMFolderMaildir::addMsgInternal (this=0xa2e9e20, aMsg=0xa570dd8, index_return=0xbfff7b3c, stripUid=false) at kmfoldermaildir.cpp:454 #16 0x01fedcdb in KMFolderMaildir::addMsg (this=0xa2e9e20, aMsg=0xa570dd8, index_return=0xbfff7b3c) at kmfoldermaildir.cpp:366 #17 0x01f5958d in FolderStorage::reallyAddMsg (this=0xa2e9e20, aMsg=0xa570dd8) at folderstorage.cpp:293 #18 0x01f5d90d in FolderStorage::qt_invoke (this=0xa2e9e20, _id=3, _o=0xbfff7c30) at folderstorage.moc:414 #19 0x02086c57 in KMFolderIndex::qt_invoke (this=0xa2e9e20, _id=3, _o=0xbfff7c30) at kmfolderindex.moc:87 #20 0x01ff1afe in KMFolderMaildir::qt_invoke (this=0xa2e9e20, _id=3, _o=0xbfff7c30) at kmfoldermaildir.moc:77 #21 0x017e5765 in QObject::activate_signal (this=0xa6d0610, clist=0xa6d0748, o=0xbfff7c30) at kernel/qobject.cpp:2355 #22 0x0208ebd0 in KMail::FolderJob::messageRetrieved (this=0xa6d0610, t0=0xa570dd8) at folderjob.moc:129 #23 0x02097fbe in KMail::ImapJob::slotGetMessageResult (this=0xa6d0610, job=0xa6efd38) at imapjob.cpp:428 #24 0x02099150 in KMail::ImapJob::qt_invoke (this=0xa6d0610, _id=2, _o=0xbfff7db0) at imapjob.moc:126 #25 0x017e5765 in QObject::activate_signal (this=0xa6efd38, clist=0xa6f1270, o=0xbfff7db0) at kernel/qobject.cpp:2355 #26 0x00ace1e4 in KIO::Job::result (this=0xa6efd38, t0=0xa6efd38) at jobclasses.moc:156 #27 0x00ab9b6f in KIO::Job::emitResult (this=0xa6efd38) at job.cpp:218 #28 0x00abb144 in KIO::SimpleJob::slotFinished (this=0xa6efd38) at job.cpp:547 #29 0x00abd422 in KIO::TransferJob::slotFinished (this=0xa6efd38) at job.cpp:912 #30 0x00ad0820 in KIO::TransferJob::qt_invoke (this=0xa6efd38, _id=17, _o=0xbfff8070) at jobclasses.moc:1050 #31 0x017e5765 in QObject::activate_signal (this=0xa430cd0, clist=0xa571890, o=0xbfff8070) at kernel/qobject.cpp:2355 #32 0x017e5604 in QObject::activate_signal (this=0xa430cd0, signal=6) at kernel/qobject.cpp:2324 #33 0x00aac837 in KIO::SlaveInterface::finished (this=0xa430cd0) at slaveinterface.moc:226 #34 0x00aaadcf in KIO::SlaveInterface::dispatch (this=0xa430cd0, _cmd=104, rawdata=@0xbfff8240) at slaveinterface.cpp:243 #35 0x00aaaa04 in KIO::SlaveInterface::dispatch (this=0xa430cd0) at slaveinterface.cpp:173 #36 0x00aa8477 in KIO::Slave::gotInput (this=0xa430cd0) at slave.cpp:300 #37 0x00aa9ef7 in KIO::Slave::qt_invoke (this=0xa430cd0, _id=4, _o=0xbfff8380) at slave.moc:113 #38 0x017e5765 in QObject::activate_signal (this=0xa436060, clist=0xa42ea18, o=0xbfff8380) at kernel/qobject.cpp:2355 #39 0x017e5ad7 in QObject::activate_signal (this=0xa436060, signal=2, param=24) at kernel/qobject.cpp:2448 #40 0x01b5a82f in QSocketNotifier::activated (this=0xa436060, t0=24) at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85 #41 0x01805194 in QSocketNotifier::event (this=0xa436060, e=0xbfff85f0) at kernel/qsocketnotifier.cpp:258 #42 0x017837eb in QApplication::internalNotify (this=0xbfff8860, receiver=0xa436060, e=0xbfff85f0) at kernel/qapplication.cpp:2635 #43 0x01782cba in QApplication::notify (this=0xbfff8860, receiver=0xa436060, e=0xbfff85f0) at kernel/qapplication.cpp:2358 #44 0x09358576 in KApplication::notify (this=0xbfff8860, receiver=0xa436060, event=0xbfff85f0) at kapplication.cpp:549 #45 0x00f54ae7 in QApplication::sendEvent (receiver=0xa436060, event=0xbfff85f0) at qapplication.h:491 #46 0x01771b3a in QEventLoop::activateSocketNotifiers (this=0x9f52b98) at kernel/qeventloop_unix.cpp:578 #47 0x0172b846 in QEventLoop::processEvents (this=0x9f52b98, flags=4) at kernel/qeventloop_x11.cpp:383 #48 0x01797816 in QEventLoop::enterLoop (this=0x9f52b98) at kernel/qeventloop.cpp:198 #49 0x01797732 in QEventLoop::exec (this=0x9f52b98) at kernel/qeventloop.cpp:145 #50 0x01783965 in QApplication::exec (this=0xbfff8860) at kernel/qapplication.cpp:2758 #51 0x0805b7a7 in main (argc=1, argv=0xbfff8a34) at main.cpp:156
Seems like a duplicate of bug #73999, but all other duplicates I found (101176, 100734, 97268, etc.) are marked "believed to be working in kmail 1.8". This was reported against 1.8.
The problem went away after a while for reasons that I could not understand, but now I cannot delete mail from the outbox. As sending mail seems to imply deleting it from the outbox, I also cannot send mail: all windows close and a message: "Ein schwerwiegender Fehler ist in KMail aufgetreten. Das Programm wird beendet." shows up (~ "A fatal error occured in kmail..."). There is no kcrash dialog, and few information on the command line: kmail: KMKernel::KMKernel kdecore (KConfigSkeleton): Creating KConfigSkeleton (0x89943b0) kdecore (KConfigSkeleton): KConfigSkeleton::readConfig() libkdenetwork: creating new pgp object libkdenetwork: Kpgp: gpg found kmail: No Qt-native utf-7 codec found; registering QUtf7Codec from libkdenetwork kmail: [void KMKernel::init()] foldersPath (from config): '/home/kebekus/linux/Mail' kmail: instantating KPIM::IdentityManager kmail: Identity::readConfig(): UOID = 1081709957 for identity named "Default" kmail: pPopFilter set kio (KSycoca): Trying to open ksycoca from /var/tmp/kdecache-kebekus/ksycoca kmail: KMailApplication::newInstance() kmail: KMKernel::openReader called QSplitter::panner 1 I QSplitter::panner 2 I QSplitter::panner 2 I QSplitter::panner 2 I kmail: [void KMail::ImapAccountBase::slotSchedulerSlaveConnected(KIO::Slave*)] kmail: WARNING: Ein schwerwiegender Fehler ist in KMail aufgetreten. Das Programm wird beendet. This is obviously quite annoying.
I believe that I found the reason for the crash of kmail: my disk quota was exceeded so that I couldn't create any new files. KMail behave normally after I removed a number of unrelated files. But of course, it would be much nicer to have a warning "Cannot create files, exiting now." rather than a crash. Best, Stefan.
*** This bug has been marked as a duplicate of 50462 ***