| Summary: | akonadi keeps loosing caldav calendars | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] Akonadi | Reporter: | Stephan Olbrich <stephanolbrich> |
| Component: | DAV Resource | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | bugs.kde.org, greg, Michael-Kiefer, muck |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Stephan Olbrich
2016-01-21 21:17:57 UTC
Do you mean that the CalDav configuration is totally lost, i.e. if you open the resource settings the URL(s) are no longer listed? Exactly. Only the CardDav URL is still there. Mmmmm, OK. This is really weird. How are the CardDAV and CalDAV URLs configured? Are they identical? Also, when the CalDAV configuration disappear can you check the configuration file (it should be named something like ~/.kde4/share/config/akonadi_davgroupware_resource_XXrc, where XX is the resource identifier)? What is the value of "settingsVersion"? Do you still have the CalDAV URLs shown in there, are they somehow mangled or just gone? It just happened again, so I could check: Both URLs are still in the file. I then restarted akonadi and now the calendars are back, although with a different color. OK, so there was an issue where the resource couldn't get the calendars on the previous sync and assumed they've been deleted. Does this happen when your network connection lags? Or when you're behind a captive portal and before being authenticated? Anything like that may explain the behavior, but I've never been able to reproduce it successfully so any bit of information helps. It is on a desktop with ethernet connection. The caldav/carddav is from owncloud running on a server in the same network. Is there any logging I could enable? Or logfiles to look at when it happens again? Yes, you can use "kdebugsettings" and enable all logs from the dav resource and kio http. Those logs will be written in your ~/.xsession-errors. I enabled dav logs but there is no kio http The full name on my station is "KIO HTTP slave (KIO)", but searching for "http" should show up only this one. Also maybe on your version you have to use "kdebugdialog" or "kdebugdialog5". in kdebugdialog5 I see kio_http and kio_http_debug. I selected both. > --- Comment #10 from Stephan Olbrich <stephanolbrich@gmx.de> ---
> in kdebugdialog5 I see kio_http and kio_http_debug. I selected both.
Yup, seems good. Note that the HTTP Authorization may be written in the logs, so remove it before sending the .xsession-errors file. Not doing so would leave your password in the clear.
This is not working. Although I only selected the two http lines in kdebugdialog5, disabled everything in kdebugdialog and only selected the dav logs in kdebugsettings my .xsession-errors is getting flooded with debug messages. I also noticed that .xsession-errors seems to gets deleted on every reboot. I have the same behavior with Debian testing. Akonadi and company seem to be version 4.14.10 here... Is anyone still having this problem with recent versions? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |