Bug 352623

Summary:	DAV-Groupware ressource crashes if the server is not reachable when akonadi comes up
Product:	[Frameworks and Libraries] Akonadi	Reporter:	jean-pierre.hoehmann
Component:	DAV Resource	Assignee:	kdepim bugs <kdepim-bugs>
Status:	CLOSED WORKSFORME
Severity:	normal	CC:	jean-pierre.hoehmann
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	Screenshot of the error dialog

Description jean-pierre.hoehmann 2015-09-12 16:58:50 UTC

I have configured a Groupware-server (Zimbra), in kOrganizer and kAddressBook which is only available through a VPN. When Kontact starts (before the VPN comes up), it will pop up a dozen Dialogs saying "Error while tring to delete calendar item. Error was: No items found." and the ressource will become unavailable in both the Calendar and the Addressbook (it dissapears completely).

Reproducible: Always

Steps to Reproduce:
1. Configure Kontact with a Zimbra instance.
2. Make the ressource unavailable.
3. Reboot and open Kontact again.

Actual Results:  
The ressources become permanently invisible in Kontact

Expected Results:  
The ressources will be available and delay sync until the server is available

The ressource dissapears in Kontact, but can still be seen in the Akonadi Console.

Akonadi states its version as 5.0.51, which is not available in the version-picker.

The server is not only unavailable, its hostname will also not resolve before the VPN comes up.

I have no special configuration that might be related.

Comment 1 jean-pierre.hoehmann 2015-09-12 17:02:48 UTC

Created attachment 94523 [details]
Screenshot of the error dialog

Comment 2 jean-pierre.hoehmann 2015-09-15 23:41:22 UTC

I do not know if this is important or not, but the error dialogs will keep appearing at boot, until the ressource is deleted via the Akonadi Console, but they do not show up everytime (if they do show up their count is exactly 10 everytime).

Comment 3 jean-pierre.hoehmann 2015-10-02 20:08:11 UTC

Bug is gone since yesterday, closing.