Bug 339444 - To-do list vanishes in Kontact frequently since 4.14 upgrade
Summary: To-do list vanishes in Kontact frequently since 4.14 upgrade
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: todoview (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-27 06:48 UTC by Matt Hilton
Modified: 2018-01-31 17:14 UTC (History)
0 users

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 Matt Hilton 2014-09-27 06:48:13 UTC
Since upgrading to version 4.14, changing between views in Kontact (say from Mail to To-do List, as I do often) results in the list of tasks being blank in the To-do list view. The list only gets restored when I switch to the Mail view, click 'Check Mail' to fetch mail manually, and then return to the To-do list view.  I am not sure exactly when the task list disappears, but I think it happens after an automatic mail check in the background (my mail is set to check at 5 minute intervals). It seems only the manual mail check restores the task list in the To-do view.

My calendars, emails, and tasks are all hosted at mykolab.com


Reproducible: Always

Steps to Reproduce:
1. Leave Kontact running, checking mail in the background automatically and wait until after a background, automatic mail check.
2. Change to To-do List view, see task list has disappeared
3. Change back to Mail view, click 'Check Mail' to do a manual mail check, and task list is restored

Actual Results:  
The above restores the task list if it has disappeared.

Expected Results:  
The task list in the To-do view should be persistent - if I change to that view, I want to see my to do list, and not have to re-fetch it from the server before I can see it.
Comment 1 Denis Kurz 2017-06-23 19:56:43 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.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 oportunity 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.
Comment 2 Denis Kurz 2018-01-31 17:14:32 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.