Bug 186020 - Participants and syncing with Google Calendar adds extra event
Summary: Participants and syncing with Google Calendar adds extra event
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 4.2.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-03 10:08 UTC by Jakob Malm
Modified: 2017-01-07 21:25 UTC (History)
1 user (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 Jakob Malm 2009-03-03 10:08:27 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

KOrganizer always adds the user as participant for each created event. When syncing an ical-calendar with a non-primary Google Calendar through GCALDaemon, the event is added to the intended Google Calendar, but an invitation is also added for the event in the primary Google Calendar.

This can be prevented by manually removing myself from the participants list when creating the event. I don't know whether this is a bug in Google Calendar, but I think there might be something strange about how KOrganizer creates the invitation, according to http://forum.kde.org/korganizer-google-calendar-and-invitations-t-34964.html#pid48908

If this is not a bug in KOrganizer, it would maybe be good to add an option to not include the user per default in the participants list.
Comment 1 Dion Moult 2009-07-11 04:26:00 UTC
I am experiencing this too.
Comment 2 Denis Kurz 2016-09-24 18:45:52 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 21:25:18 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.