Bug 378514 - No network at startup -> No mail
Summary: No network at startup -> No mail
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 5.4.3
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-06 18:34 UTC by Axel Braun
Modified: 2020-12-25 15:59 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Braun 2017-04-06 18:34:31 UTC
Boot the Laptop and log in.
In case you have a Wifi connection where the password in Kwallet has to be entered first AND Akonadi has already started, no mail is being fetched afterwards. Even not after half an hour
Switching on- and offline mode does not help either.
Workaround: Close KMail, open a terminal window and issue akonadictl stop.
This is nothing for a less experienced user, so please fix this
Thank you!
Comment 1 Axel Braun 2017-11-24 14:17:33 UTC
The isse still occurs with KMail 5.6.3.
After a reboot, and login to KDE I needed to login to a public network, which took some time. Bringing up KMail and sending a newly composed mail, KMail freezes completely and has to be killed by process management. (Thats why I consider this a crash)
akonadictl restart did not help
akonadiconsole and restarting the agent for sending mail did not help

Only workaround: using the RF kill switch to disconnect from WIFI, sending mails (which end up in the outbox in that case), enabling network again and then sending mail in outbox. Suprisingly, that works. Looks like Kmail cant detect the network status properly
Comment 2 Justin Zobel 2020-12-17 05:32:50 UTC
Thank you for the crash report.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Comment 3 Axel Braun 2020-12-25 15:59:11 UTC
Looks like that this bug - after nearly 3 years untouched - is gone as well.