| Summary: | KMail 4.14.9 hangs when sending (signed) message | ||
|---|---|---|---|
| Product: | [Applications] kmail2 | Reporter: | Axel Braun <axel.braun> |
| Component: | commands and actions | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | grave | ||
| Priority: | NOR | ||
| Version: | 5.6.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Axel Braun
2015-06-29 10:43:10 UTC
Having had some trouble with the 'hang on send' , my impression is that it is not necessarily related to GPG signature, but has to do with network connectivity - if you have used KDE without network, it is more likely to hang. After killing a hanging KMail and restarting akonadi, turning KMail into offline mode and switching the network physically off with the RF kill switch, I can use KMail sending the mails that previously hang (at least into the send folder). As soon as I turn the network on (KMail still in offline mode), the sending of mails hangs again. Rebooting the PC does not help. Appears in 4.14.10 as well This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life. Just had the same issue this morning: Starting up KMail 5.5.1 including Akonadi, pick on mail, answer, set 'sign Message and hit 'send'. Sandclock turns, and KMail is blocked. I can see in the main screen that new messages arrive, but I have to kill KMail completely to interact (work) with it again. Sadly, most part of the message intended to send is lost.... Sorry, was already KMail 5.5.2 And another info...it is not necessary to sign a mail, happens as well with unsigned mails. I started kontact from the console, but at the time when trying to send the mail, no messages appear in the terminal. Same symptoms appear when the network connection is not there when you start kontact, e.g. because you have to log into the Wifi first, or authenticate in the browser Actually this is still an issue on KMAil 5.6.0 After startup of the Laptop I first have to log in on a webpage to get internet access. When I send a mail the whole frontend freezes, although I see notifications that new mails are coming in. My guess is that Kmail does not properly detect once it is online or offline. If I use the killswitch of the laptop to physically disconnect all network, start kmail and write a mail, 'send' command puts it into the outbox. Once network is turned on, I can use 'send mail in outbox'. That works. But next mail I write fucks it up again. Not to mention that you lose the mail content you have just composed.... removing crypto, as it fails as well without crypto In 5.8.2 I found that sending is completely blocked (you have to kill the kmail-process!) if the S/MIME certificate that is set in the identity is expired. Once the certificate is removed, everything works as expected. I guess this is causing the big timeouts when sending as well. Can you verify this? Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Seems to work in between |