https://bugs.kde.org/show_bug.cgi?id=488493
Daniel K <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|DUPLICATE |--- CC| |[email protected] Status|RESOLVED |REOPENED Ever confirmed|0 |1 --- Comment #2 from Daniel K <[email protected]> --- Reopening — this is not fully fixed by 522164 I'm still seeing this exact error on a fully up-to-date system: KDE Plasma 6.7.3 akonadi-server 26.04.3 (Fedora 44) STEPS TO REPRODUCE: Create a new event in KOrganizer, synced via Akonadi Google Resource (same calendar, no collection change). Immediately edit the event (via the edit dialog, changing date/time) — no calendar/collection switch involved. Save. OBSERVED RESULT: -------------------------------------------------------------------------------- Error while trying to modify calendar item. Error was: [LLCONFLICT] Resource akonadi_google_resource_0 tries to modify item ... with revision 0; the item was modified elsewhere and has revision 1, aborting STORE. -------------------------------------------------------------------------------- The event never syncs the change to Google Calendar; the change is stuck locally afterwards. The fix for bug 522164 (commit 5571f7a2b, "Don't LLCONFLICT when moving an incidence to a new collection") appears to specifically address moving an event to a different collection. My case involves no collection change at all — just modifying date/time within the same Google-synced calendar — and the LLCONFLICT still occurs. This suggests the original 488493 report describes a separate (or at least not fully overlapping) code path from 522164, and reopening seems warranted. Happy to provide further logs/screenshots if useful. -- You are receiving this mail because: You are watching all bug changes.
