Summary: | kmail crashes when downloading messages | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Bipin <bipinbabu> |
Component: | pop3 | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED REMIND | ||
Severity: | crash | CC: | christophe |
Priority: | NOR | ||
Version: | 1.9.1 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Bipin
2006-07-10 22:21:35 UTC
KMail seems to crash when it is downloading messages from your POP account. Which POP server are you using? Does it help to check less often for new mail? Its an MS server, not sure which one in specific though. "Does it help to check less often for new mail?" Actually it is set to query for new mails every 1 mint. I have a problem with this also, I get my mails with an easy delay of atleast 10 mints compared to people using other applications (thunderbird). I do not have any definite proof for you to replicate it, this is something you will have to experience. Since I am using KMAIL in a production environment, it would be difficult for me to check mails less often. If your mail arrives delayed then it could be that KMail has a problem with your POP server. Maybe the connection isn't closed correctly for some reason and therefore the connection has to timeout. And only after the timeout the next mail check is started. Could you probably check e.g. with "netstat -tap | grep pop" whether the connection to the server stays open even though the check seems to have finished? Does KMail actually check every minute or probably only every 10 minutes or so? (Watch the information in the status bar which prints a timestamp after each check for new mail.) I would definitely monitor this and send you the report....by end of this week...just a bit busy at work... Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1247921616 (LWP 5036)] [New Thread -1280410720 (LWP 5040)] [New Thread -1272018016 (LWP 5039)] [New Thread -1263625312 (LWP 5038)] [New Thread -1255232608 (LWP 5037)] [KCrash handler] #6 0xb7ca0998 in KMFolderIndex::setIndexEntry (this=0x82d1e78, idx=7100, msg=0x8917c40) at ./kmail/kmfolderindex.cpp:476 #7 0xb7bb1756 in FolderStorage::unGetMsg (this=0x82d1e78, idx=7100) at ./kmail/folderstorage.cpp:543 #8 0xb7b7b97e in KMFolder::unGetMsg (this=0x82d1c88, idx=7100) at ./kmail/kmfolder.cpp:313 #9 0xb7dd54af in KMAccount::processNewMsg (this=0x81cd400, aMsg=0x8917c40) at ./kmail/kmaccount.cpp:259 #10 0xb7becee5 in KMail::PopAccount::slotProcessPendingMsgs (this=0x81cd400) at ./kmail/popaccount.cpp:320 #11 0xb7bed062 in KMail::PopAccount::processRemainingQueuedMessages ( this=0x81cd400) at ./kmail/popaccount.cpp:794 #12 0xb7d96fc3 in KMail::PopAccount::slotJobFinished (this=0x81cd400) at ./kmail/popaccount.cpp:655 #13 0xb7d98b39 in KMail::PopAccount::slotResult (this=0x81cd400) at ./kmail/popaccount.cpp:981 #14 0xb7dfa119 in KMail::PopAccount::qt_invoke (this=0x81cd400, _id=9, _o=0xbfc734c4) at ./kmail/popaccount.moc:120 #15 0xb733cb5d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #16 0xb63930ee in KIO::Job::result () from /opt/kde3/lib/libkio.so.4 #17 0xb63d1c4d in KIO::Job::emitResult () from /opt/kde3/lib/libkio.so.4 #18 0xb63e529e in KIO::SimpleJob::slotFinished () from /opt/kde3/lib/libkio.so.4 #19 0xb63e599d in KIO::TransferJob::slotFinished () from /opt/kde3/lib/libkio.so.4 #20 0xb63d187a in KIO::TransferJob::qt_invoke () from /opt/kde3/lib/libkio.so.4 #21 0xb733cb5d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #22 0xb733d7bd in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #23 0xb638c3ac in KIO::SlaveInterface::finished () from /opt/kde3/lib/libkio.so.4 #24 0xb63fa0a5 in KIO::SlaveInterface::dispatch () from /opt/kde3/lib/libkio.so.4 #25 0xb63f7fda in KIO::SlaveInterface::dispatch () from /opt/kde3/lib/libkio.so.4 #26 0xb63a08bc in KIO::Slave::gotInput () from /opt/kde3/lib/libkio.so.4 #27 0xb63e9250 in KIO::Slave::qt_invoke () from /opt/kde3/lib/libkio.so.4 #28 0xb733cb5d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #29 0xb733d6c2 in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #30 0xb7674ab0 in QSocketNotifier::activated () from /usr/lib/qt3/lib/libqt-mt.so.3 #31 0xb735ad80 in QSocketNotifier::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #32 0xb72ddc47 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #33 0xb72dea11 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #34 0xb79868e3 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #35 0xb72d2884 in QEventLoop::activateSocketNotifiers () from /usr/lib/qt3/lib/libqt-mt.so.3 #36 0xb728d644 in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #37 0xb72f4a78 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #38 0xb72f490e in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #39 0xb72dd7ff in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #40 0x0804a0cd in main (argc=0, argv=0x0) at /usr/src/debug/kdepim-3.5.1/kmail/main.cpp:110 #41 0xb6ede87c in __libc_start_main () from /lib/libc.so.6 #42 0x08049e41 in _start () Same here: crashes on every POP since today in the morning. I'm using TLS-enabled pop3 with clear-text passwords. Automatic pop is disabled. Netstat doesn't show open pop connections. I've also tried removing every (find .kde | grep -i kmail) config file and the ~/Mail folder without success. I ran the netstat command to check the status of the connection. The problem is that Kmail does check for mail every 1 minute, but it take a solid of 3 mints to complete the check. For instance it started to check at 7:24:59 Am and that check ended at 7:27:51Am. I am not sure why. Do we have any option for enabling some debug commands to see what happens at the backend? I believe debian provides debug-enabled packages named <modulename>-dbg, so installing kdelibs-dbg and kdepim-dbg should allow you to get some debug information. You might need to set the environment variable "KDE_FORK_SLAVES" in order to get the debug info from the ioslaves to go to the controlling terminal so you can see it. BTW, does the crash still occur if you turn off interval mail checking? Could we get feedback please ? Does this crash still occur with a recent kmail version ? Christophe/Philip, Sorry but I've moved from using Kmail to other email clients. Its been quite a while and I don't intend to look into Kmail anytime soon. Sorry for not being able to contribute much towards this bug. Thankyou so much for looking into this. Thank you for your feedback. Closing this bug for now. |