Summary: | Kmail can not check for new mail after awakening of my PC after suspend. | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Alexander <vo.zaeb> |
Component: | IMAP | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | halla, martin+kde, remur, simon, vo.zaeb |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Example. |
Description
Alexander
2010-07-01 09:06:08 UTC
Seems that this not only after suspend. Kmail is running all day and randomly hangs, but kill -ABRT helps. Application: KMail (kmail), signal: Aborted [KCrash Handler] #5 0x00007f8b584480b3 in select () from /lib/libc.so.6 #6 0x00007f8b599d687a in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timeval const*) () from /usr/lib/libQtCore.so.4 #7 0x00007f8b599db702 in QEventDispatcherUNIXPrivate::doSelect(QFlags<QEventLoop::ProcessEventsFlag>, timeval*) () from /usr/lib/libQtCore.so.4 #8 0x00007f8b599dc2ff in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #9 0x00007f8b58e49ea2 in ?? () from /usr/lib/libQtGui.so.4 #10 0x00007f8b599b0122 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #11 0x00007f8b599b035c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #12 0x00007f8b599b476b in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #13 0x0000000000403108 in _start () It happens only with gmail's accounts. I have three gmail's accounts and one on an another service, and only gmail accounts hangs. 1. Previous comment is lie, this happens for all accounts. 2. This happens even after DSL reconnection. Created attachment 49316 [details]
Example.
This operation never be completed and I can't cancel it, only killall kmail can help.
This is similar to the file copying dialog in Windows, you just need fix one thing — add this string "will be completed across 32423 days" or something like that...
By the way, I have to ask, someone working on it? Because looks like kmail is died.
I think, the second comment explains why this is happening — http://chenthill.wordpress.com/2010/01/11/evolution-with-improved-imap-support-imapx/ Quote: ... If you close the lid on your laptop so that it suspends for a few hours and then open it, all the tcp-sessions will have timed out on the server but Evolution may still think that they are alive and try using them. This leads to very long timeouts before Evolution works correctly again after a resume. I confirm this under 4.4; kmail 4.6 beta doesn't seem to be affected (or the timeout is a lot shorter). I think these are duplicates: https://bugs.kde.org/show_bug.cgi?id=242598 https://bugs.kde.org/show_bug.cgi?id=265313 with 1.13.7 on KDE 4.7 it definitly still and always happens: after suspending my laptop I always have to restart kmail in order to get my imap mail again. happens also with latest git, btw why is this still set to unconfirmed Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback. |