[Kolab-devel] [issue4821] Sync conflict: Resolving with "newest" can lead to an assert

[aheinecke]

When resolving a conflict the resolve conflict dialog shows up twice and
afterwards the appointment is appearently "gone".

This bug is similar to:
https://roundup.kolab.org/issue4819

But instead of losing the appointment it now just gets "hidden" from the UI the
groupware object is _not_ deleted it stays on the server and is shown in the
clients folder in Kmail. It just dissapears from Korganizer. Regardless of
syncing it is then only shown again after a restart of Kontact.

Kontact Version: enterprise35 20120224.6bc84f7

User A has a calendar that user B has full access to.

Steps to reproduce:
User A creates an appointment
User B Syncs
User B modifies the appointment
User A modifies the appointment
User A uses take newest to resolve the conflict.
-> A Second conflict dialog 
User A clicks take newest in the second conflict dialog.
-> Appointment dissapears.

On the console:

QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
ASSERT: "!resource.isEmpty()" in kmailicalifaceimpl.cpp (832)
QGDict::hashKeyString: Invalid null key

Kontact does not crash.

More debug output etc. can be created on request.

----------
assignedto: emanuel
keyword: enterprise35, kde client
messages: 28582
nosy: aheinecke, allen, emanuel, laurent, ludwig, sergio, till, vkrause
status: unread
title: Sync conflict: Resolving with "newest" can lead to an assert

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://roundup.kolab.org/issue4821>
______________________________________