Summary: | events not synced when created without network | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Sebastien Renard <renard> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | grave | CC: | kdepim-bugs, killian.de.volder |
Priority: | NOR | ||
Version: | 4.10 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Sebastien Renard
2013-03-23 15:50:56 UTC
Precision: in akonadiconsole, on DB Browser tabs, the mlissing event have the dirty columns set to 1. 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? 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. 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. 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. Ow and this with version akonadi 1.12.0 and 1.11.0 (other version not tested yet). 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. 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. |