Bug 341333 - warning when DAV resource goes out of sync
Summary: warning when DAV resource goes out of sync
Status: RESOLVED DUPLICATE of bug 338570
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: DAV Resource (show other bugs)
Version: 4.13
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-27 19:51 UTC by Malte Dik
Modified: 2015-08-19 21:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Malte Dik 2014-11-27 19:51:29 UTC
Hi,

a notification when a calendar or addressbook goes out of sync (e.g. because of merge conflict) would be nice. At the moment the only way seems to be to look into the //Akonadi Configuration// dialog. If there is a green circle it is fine, if there is an unplugged plug it is not fine. Really? A notification via the KDE notification system, a change of the akonaditray widget would be nice.

Or a hint in which logs to look so I can build something on my own.

Thanks in advance,

Malte

Reproducible: Always

Steps to Reproduce:
1. Make different changes from different accounts on the same DAV source within one refresh cycle


Actual Results:  
Akonadi stops syncing without notifying the user.

Expected Results:  
Akonadi notifies the user.
Additionally maybe switching the cached items to read-only.

Formally I know this is a wishlist item, but operationally I think this is critical. I will leave it up to you where to sort it in, but I think this is an important improvement/fix to make.

As I said, I'd be happy to script something if I could get the needed info (resource connected/in-sync or not) via something similar to "akonadictl status" or a log file.
Comment 1 Grégory Oestreicher 2015-08-19 21:49:15 UTC
The conflict resolution dialog has been implemented, but I forgot to merge this bug.

*** This bug has been marked as a duplicate of bug 338570 ***