Created attachment 116880 [details] IRC Discussion about the bug SUMMARY When using google as calendar service (google calendar configured, "use groupware communication"), 2 things happen when one receives an invite. STEPS TO REPRODUCE 1. When accepting the invite, the calendar entry is Hijacked and one is entering the appointment as organizer, and sending out that Acceptance with a full calendar entry (ics-file) to all attendees 2. If any of these attendees Accepts your hijacked calendar entry, and you add these to the calendar (the acceptance), a new calendar entry is added to the google calendar and all attendees receive a new mail (snowball system). OBSERVED RESULT - One becomes the Owner (organizer) of the calendar entry very fast, and receives tons of rejected/accepted mails from all other attendees. - When Manipulating any of these acceptance mails, one starts the process again, cause duplicate, tripple, quadruple etc. entries in the calendar. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: KUbuntu 18.10 (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION See discussion in IRC chat (added as text attachment).
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!