Bug 347406 - Invitation of MS-Outlook is inserted into calendar but is not synchronized
Summary: Invitation of MS-Outlook is inserted into calendar but is not synchronized
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: invitations (show other bugs)
Version: 4.14.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-08 08:17 UTC by Torsten Bielen
Modified: 2018-01-31 17:14 UTC (History)
0 users

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 Torsten Bielen 2015-05-08 08:17:04 UTC
I use the akonadi-resource google-calendar-and-task. 

If I get an invitation from a MS-Outlook per mail  and accept it the invitation is inserted into the google-calendar (locally). But the event is not synchronized. I don't see the meeting in other sync. devices. If the invitation comes from a kontact client the synchronisation works.

My first assumption was the private calendar is used but the used resource is the google-calendar.  Meetings inserted directly are synchronized without any problem. Also events come from other devices are synchronized.

In the configuration "E-Mail various" (in german "Verschiedenes") all options are selected besides "Exchange compatible naming....".
------------------------
Kontakt: 4.14.6
opensuse 13.2 (64-bit)

Reproducible: Always

Steps to Reproduce:
1. Use google calendar resource 
2. Send a invitation with MS-Outlook 
3. Accept the invitation, change to the calendar view of kontakt.
4. You see the the new meeting.
5. Open the web interface of the google calendar.
6. The meeting is not available (not  synchronized).

Actual Results:  
Meeting is not synchronized.
Comment 1 Denis Kurz 2017-06-23 20:02:42 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-01-31 17:14:53 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.