https://bugs.kde.org/show_bug.cgi?id=419713
quentin.aymar...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |quentin.aymar...@gmail.com
--- Comment #10 from quentin.aymar...@gmail.com ---
It seems this bug is still very much alive. I discovered today that KOrganizer
seems to silently delete random shared events from Google Workspace with no
prompt whatsoever. I learned so when a colleague stated that his meeting from
the afternoon disappeared from the calendar. When browsing through Google
Workspace logs I saw I was the one causing it.
Using various filters I identified at least a dozen of similar deletions in the
past few months, none of which have been reported by my colleagues.
Investigating the cause of the deletion was not easy : I have obviously no
memory of what I was doing for past events, but for the one of today I am
absolutely certain I was not using the calendar at time of deletion. Plus, the
User Agent logged by Google does not correspond to what my Firefox advertise. I
then explored the possibility that one of my desktop/mobile calendar app was
causing the problem. Thunderbird is locked in read-only mode for shared
calendars (in order to avoid mistakes) so unlikely.
However KOrganizer was always running in the background. I stopped using KDE
PIM for work a few month ago due to a high number of bugs, unexpected
behaviors, etc so at that time I removed my Google Workspace account from
Kmail. However, it seems that doing so did not also remove my Google account
from KOrganizer. Since I still have a KOrganizer instance running in the
background for local-only events, it seems to have persisted deleting random
stuff from time to time, until I noticed it today.
I removed my Google Account from KOrganizer and set up an alert on similar
events in Google's security center. This issue caused quite the confusion, I
hope to see it gone now, but I thought it should be adequate to update this old
bug to provide the info that similar symptoms are still very much happening
today.
--
You are receiving this mail because:
You are on the CC list for the bug.
