Bug 119549 - appointment cancellation not registered correctly with kolab2 resources
Summary: appointment cancellation not registered correctly with kolab2 resources
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Kolab Resource (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-05 09:44 UTC by T. Ribbrock
Modified: 2013-07-12 15:08 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description T. Ribbrock 2006-01-05 09:44:19 UTC
Version:            (using KDE KDE 3.5.0)
Installed from:    SuSE RPMs
Compiler:          gcc (GCC) 4.0.2 20050901 (prerelease) (SUSE Linux) 
OS:                Linux

This bug occurs when using korganizer (kontact) in conjunction with a kolab2 (server version 2.0.1) resource.
kontact/kmail/korganizer were set up for kolab2 using kolabwizard and confirmed to be working.

Steps to show the bug:

1) User A creates an appointment in the kolab2 calendar with user B as attendee
2) User B gets the invitation and confirms
3) User A gets the confirmation and lets it be registered in his calendar
4) User A now deletes the appointment
5) User B gets a cancellation mail and chooses "Delete this appointment from my calendar"
6) The appointment does *not* get deleted. In fact, if user B tries to delete the appointment manually, this fails unless he removes himself from the list of attendees first.

This bug has already been fixed in the kde-client of the kolab2 team (kdepim-3.3.proko2.0.4), see bugs 900 and 992 in their bug tracker: https://intevation.de/roundup/kolab/issue900 and https://intevation.de/roundup/kolab/issue992
Comment 1 Reinhold Kainhofer 2006-11-02 19:00:06 UTC
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 2 Christian Mollekopf 2013-07-12 15:08:38 UTC
Please reopen if the problem is still present in a recent version (>= 4.10), but I think it's not.