SUMMARY *** Calendar resource not changing back from offline state *** STEPS TO REPRODUCE 1. Setup nextcloud CalDAV resource in contact 2. Wait for a while (resource goes to offline) 3. Wake machine up and there is no way to get the resource back to online OBSERVED RESULT Resource stays offline (whatever that means, since cron jobs with rsync work fine) EXPECTED RESULT Resource changes back to online by itself fast. I use akonadiconsole now to restart the agent (however that is not an option for a normal user when it first shows a severe warning) SOFTWARE/OS VERSIONS Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 5.15.0-56-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics Memory: 15,0 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: Acer Product Name: Aspire A515-45G System Version: V1.08 ADDITIONAL INFORMATION Same for contacts
Getting same problem. In settings the error was "There was a problem with the request. The item has not been created on the server. The file or folder dav.***.*** does not exist. (0)." However, if I try to modify the setting it will perfectly fetch every caldenar I have on the server, but still insist on keeping it offline. Currently I can only make it work again by deleting it and adding it again.
Hi coding-matter@mailbox.org, you can use akonadiconsole to restart the agent and get it back online. Start akonadiconsole from the command line, ignore the warning (but be very careful what you are doing), locate the CalDav/CardDav agent (the icon will be a folder with a map of earth in it), right click and choose restart agent. This will restart the agent, cause it to get all collections (address books and calendars) and start syncing. This is no option for a normal use to restart the agent, though.
Thank you Uwe Köhler! However, our cases might be different, however, with the akonadiconsole you suggested, I find in my case something even more weird. Use it to restart my dav does not change the situation, however if I use akonadiconsole to clone the agent, the new agent works perfectly fine, and all I need to simply delete the old agent. Anyway now I have a workaround as well and thank you very much!
(In reply to coding-matter from comment #3) > Thank you Uwe Köhler! > > However, our cases might be different, however, with the akonadiconsole you > suggested, I find in my case something even more weird. > > Use it to restart my dav does not change the situation, however if I use > akonadiconsole to clone the agent, the new agent works perfectly fine, and > all I need to simply delete the old agent. > > Anyway now I have a workaround as well and thank you very much! Great that I could help with a workaround. If our cases are different, it might be better to create a new bug report with a detailed description of your problem.