Version: (using KDE Devel) Installed from: Compiled sources Yesterday kmail worked fine, but after a cvs update it doesn't start anymore. (From time to time it starts, but most of the time it fails.) I get this on konsole: hal@hal:~/download/kde3/cvs$ kmail kmail: No Qt-native utf-7 codec found; registering QUtf7Codec from libkdenetwork kmail: instantating IdentityManager kmail: KMIdentity::readConfig(): UOID = 0 for identity named "Default" kmail: KMIdentity::readConfig(): UOID = 938112923 for identity named "Stephi" kmail: pPopFilter set ERROR: Communication problem with kmail, it probably crashed. Last lines of strace: kmail: pPopFilter set "\2\4\0\2\0\0\0\0", 8) = 8 read(3, "\1\0\0\0", 4) = 4 write(2, "ERROR: Communication problem.... .xsession-errors: DCOP: register 'kmail' -> number of clients is now 22 DCOP: register 'anonymous-7280' -> number of clients is now 23 DCOP aborting call from 'anonymous-7280' to 'kmail' DCOP: unregister 'kmail' DCOP: unregister 'anonymous-7280' I tried removing the lock file and restarted kde with a kill -s9 of all kdeinit programs.
After a cvs update of what? Only kdepim? Or also kdelibs? Does going back to a previous cvs state fix the problem? I suppose you don't get a backtrace, right?
I don't get a backtrace right. That is the biggest problem for me. I've done an update of my complete kde tree (support, libs, base, net, pim and others) I haven't tried to go back, I think I have to do that with the "x days old" option of cvs right ?
My crash is very similar and I do get a stack trace. libkdenetwork: creating new pgp object libkdenetwork: Kpgp: gpg found kmail: No Qt-native utf-7 codec found; registering QUtf7Codec from libkdenetwork kmail: instantating IdentityManager kmail: KMIdentity::readConfig(): UOID = 0 for identity named "Default" kmail: pPopFilter set kmail: kmfoldermbox.cpp:427: virtual int KMFolderMbox::unlock(): Assertion `mStream != 0' failed. ERROR: Communication problem with kmail, it probably crashed. [New Thread 1100311104 (LWP 23803)] 0xffffe002 in ?? () #0 0xffffe002 in ?? () #1 0x415114b9 in KCrash::defaultCrashHandler(int) () from /usr/local/kde3/lib/libkdecore.so.4 #2 <signal handler called> #3 0xffffe002 in ?? () #4 0x42028b93 in abort () from /lib/tls/libc.so.6 #5 0x42020f95 in __assert_fail () from /lib/tls/libc.so.6 #6 0x081b15d6 in KMFolderMbox::unlock() () #7 0x081adada in KMFolderMbox::close(bool) () #8 0x080a1b6a in KMFolderIndex::fillDictFromIndex(KMMsgDict*) () #9 0x08143c01 in KMFolder::fillMsgDict(KMMsgDict*) () #10 0x0816fd0f in KMFolderMgr::invalidateFolder(KMMsgDict*, KMFolder*) () #11 0x0816fdf0 in KMFolderMgr::readMsgDict(KMMsgDict*, KMFolderDir*, int) () #12 0x0816fe33 in KMFolderMgr::readMsgDict(KMMsgDict*, KMFolderDir*, int) () #13 0x0809cbdd in KMKernel::msgDict() () #14 0x0819c15e in KMMsgList::clear(bool, bool) () #15 0x080a1aa3 in KMFolderIndex::clearIndex(bool, bool) () #16 0x08142be3 in KMFolder::remove() () #17 0x0816f475 in KMFolderMgr::removeFolderAux(KMFolder*) () #18 0x0816f29a in KMFolderMgr::remove(KMFolder*) () #19 0x0809a13a in KMKernel::cleanupImapFolders() () #20 0x08099615 in KMKernel::init() () #21 0x08095275 in main () #22 0x420156a4 in __libc_start_main () from /lib/tls/libc.so.6 Maybe this will help.
Should be fixed in cvs in the meantime. Closing.