Bug 317237 - events not synced when created without network
Summary: events not synced when created without network
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.10
Platform: Compiled Sources Linux
: NOR grave
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-23 15:50 UTC by Sebastien Renard
Modified: 2017-01-07 22:11 UTC (History)
2 users (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 Sebastien Renard 2013-03-23 15:50:56 UTC
When there's not network available, events created in calendar are not synced when network is available.
Restarting agent or akonadi or doing "synchronize all" does not sync it.. Event keeps local and is never sync with google agenda.
Looking in akonadiconsole, those event have not remoteid (value is empty).

This is very anoying, because you can't "full sync" again the whole calendar. So you're remote calendar is not reliable at all, some events are missing.


Reproducible: Sometimes

Steps to Reproduce:
1. Disconnect network
2. Create some event in korganizer
3. Reconnect to network

Actual Results:  
Look to https://www.google.com/calendar or any other device synced to google (like an android phone for instance). Event is not there.


Expected Results:  
Event should be created as well on google agenda.

Open akonadiconsole and find event : it does not have remoteid.
Comment 1 Sebastien Renard 2013-03-23 15:56:55 UTC
Precision: in akonadiconsole, on DB Browser tabs, the mlissing event have the dirty columns set to 1.
Comment 2 Daniel Vrátil 2013-06-01 00:18:31 UTC
I'm unable to reproduce this problem with current KDE PIM 4.10 and LibKGAPI 0.4.4/2.0.0.

In general, it sounds more like Akonadi issue. The idea is that if a resource reports, that it requires internet connection to work, Akonadi will hold the change notification until network is available and send it to the resource when you connect to network.

Are you sure that NetworkManager correctly reports your connection status? Does the change replay work with another online resources, like IMAP?
Comment 3 Sebastien Renard 2013-06-02 20:32:37 UTC
Yes, status seems good as other events created after are properly synced on the remote side.
BTW, i use libkgapi 0.4.4. I did not test 2.0 yet.
Comment 4 Sebastien Renard 2013-11-28 22:03:07 UTC
Hello,

I switch to owncloud (bye bye google) and reproduce this bug again. Some events don't sync on remote side. And when i open akonadi console, those events have empty remoteid.
Comment 5 Killian De Volder 2014-04-10 11:36:35 UTC
I also have this bug.
Disconnect network, make item, reconnect network -> No syncronization.
Items have dity=1 and remoteId is nul.
Restarting akonadi doe not help, akonadictrl fsck does not help, sync does not help.
Editing the item does help.

What can also cause this issue is if the server is down/bugged, where it reports an error to the client. (This is what caused it for me, as i'm usually online.)

Personally I suspect the issues is simple: caldav items are only synced during create/edit. Not during update. Imo update should just check for dirty items, and try to add them to the remote if the remoteId is empty.
Comment 6 Killian De Volder 2014-04-10 11:40:07 UTC
Ow and this with version  akonadi 1.12.0 and 1.11.0 (other version not tested yet).
Comment 7 Denis Kurz 2016-09-24 20:45:16 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 8 Denis Kurz 2017-01-07 22:11:08 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.