Bug 468654 - After upgrading to KDE 5.27, my mailboxes always show up as (Offline) after computer wakes up from sleep. No way to bring them back online.
Summary: After upgrading to KDE 5.27, my mailboxes always show up as (Offline) after c...
Status: REPORTED
Alias: None
Product: kontact
Classification: Applications
Component: mail (show other bugs)
Version: 5.22.3
Platform: Neon Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-04-18 14:43 UTC by ioo+kde
Modified: 2023-04-18 14:43 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description ioo+kde 2023-04-18 14:43:32 UTC 
SUMMARY
***
After upgrading to KDE 5.27, my mailboxes always show up as (Offline) after computer wakes up from sleep. Right clicking and selecting "Update this folder and all subfolder" gives the message: "Before syncing folder: xx it is necessary to have the resource online. Do you want to make it online? If I click "Go online" nothing happens. The mailbox remains offline.

The only way I have found to being the mailbox back online is to reboot the computer. This is not an acceptable solution. I will likely need to start looking for another mail client if Kmail is broken in 5.27.
***


STEPS TO REPRODUCE
1. Wake computer up from sleep
2. Open Kontact
3. Try to check mail and notice it says (offline)
4. Right click and select "Update this folder"
5. Click "Go online"
6. Nothing happens, mailbox is still offline.

OBSERVED RESULT
- Mailbox will not go online automatically when waking up from sleep
- Mailbox will not go online after selecting "Go online"

EXPECTED RESULT
Mailbox should go online automatically. Certainly it should go online if I specify it to go online which it also does not do.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon 5.27
(available in About System)
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
This is a new issue, it has never happened before the recent disut upgrade to KDE 5.27