Bug 153966 - Double calendar entries even so only one configured calendar is marked active
Summary: Double calendar entries even so only one configured calendar is marked active
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: OpenXchange Resource (show other bugs)
Version: 4.11
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2007-12-13 14:33 UTC by Michael Krueger
Modified: 2017-01-07 21:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Krueger 2007-12-13 14:33:15 UTC 
Version:           Unbekannt (using KDE 3.5.8 "release 21.2" , openSUSE )
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.18.8-0.7-default

I have two calendars configured:
a) "Standard Resource from KOrganizer"
b) My Company Kalendar which is OPEN-XCHANGE 5607 (hymalia)

I have only my company calender selected.
Now when I create a new appointment, I get confirmation dialog that a new appointment has been created, twice. Not sure why, but could it be, that KOrganizer does try to create the appointment twice because I have two calendar resources defined, even so I'm only using one of them?

Anyway, after appointment creation I get also two confirmation mails from OX-Change which tells me that not only the dialog in KOrganizer did show twice, but also the request to create the appointment was sent twice to the Open-Exchange server.

Please fix this if possible. Thanks...
Comment 1 Michael Krueger 2007-12-14 13:58:41 UTC 
Can I help to reproduce this? Any more details required?
Comment 2 Michael Leupold 2008-09-28 22:03:13 UTC 
Unfortunately the OpenChange resource is currently not working because of the rewrite as an Akonadi resource. I never experienced something like that with other resources. Does this problem still happen for you or did it vanish with 3.5.9 or 3.5.10 release?
Comment 3 Michael Krueger 2008-09-29 06:40:07 UTC 
Hi,

yes the problem is still there. For KDE4 - which I'm now mostly using, other issues came up like: 167677

Thanks for trying to fix this. We run the groupware server in our office. If I can help, please let me know.

Regards,
Michael
Comment 4 Denis Kurz 2016-09-24 20:34:05 UTC 
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 5 Denis Kurz 2017-01-07 21:51:15 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.