Recently I was in some situation where I did not have any network connection at all or was within a LAN that was not connected to the internet. Therefore communication with my usual ressources (IMAP and CalDAV/CardDAV) was not possible. For the IMAP case there is a simple solution as one can just set KMail to offline mode but for Cal/CardDAV akonadi was still trying to poll the corresponding servers, causing an annoying notification in the notification bar every some minutes. I was searching around if there is some feature to set the akonadi service into some "offline" state but couldn't find any. The only soltuion I found was to stop the whole akonadi service via "akonadictl stop" but this would also make my KMail no longer useable. Therefore it would be very nice if there was such a "set akonadi offline" function that can be clicked or even something that automatically asks after some not successfull sync runs if one wants to set akonadi offline. This could also be of use if one knows that a certain ressource is temporarily not available for some reason. Reproducible: Always
It is possible to set individual resources to an offline mode (for example via Akonadi Console) - so this should be fixed in KOrganizer and KAddressbook to have a GUI to switch to offline mode, like KMail.
I happen to be quite often disconnected from the internet. Thus I would wish that Caldav and Carddav resources recognize it by themselves and switch to offline-mode automatically.
One more think. Sometimes it happens that both Caldav and Carddav resources seem not to work properly when there are problems with the internet connection. In these cases address books and calenders hosted on my ownCloud server are not shown locally. Is there no caching mechanism to provide a local copy of calendar and address book entries?
Sorry, I forgot to mention that I'm running KDE 4.14.5 and Akondi 1.13.0 on an up-to-date Chakra Linux.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
For me, the problem is no longer relevant
Well, I did not get any annoying error messages for a while. Thus I suppose this has been solved.