[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2024-02-07 Thread Rigo Wenning
https://bugs.kde.org/show_bug.cgi?id=406917

--- Comment #19 from Rigo Wenning  ---
Akonadi is unfit for synchronization. If you use nextcloud or any other remote
calendar, you risk your data. This is known to me and wasn't fixed since 10
years now and that's why I unfortunately had to abandon KDE-PIM. Since then, no
issue whatsoever with my remote calendar. Akonadi is just not usable for
production. Too much play and candy, too little serious protocol work.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2024-02-06 Thread Roman Zimmermann
https://bugs.kde.org/show_bug.cgi?id=406917

--- Comment #18 from Roman Zimmermann  ---
Definitely not fixed. I’m still experiencing this regularly. My last attempts
to make this work again lead to losing my entire calendar. :-/

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2023-10-10 Thread Roman Zimmermann
https://bugs.kde.org/show_bug.cgi?id=406917

Roman Zimmermann  changed:

   What|Removed |Added

 CC||toro...@gmail.com

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2021-10-15 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406917

aux...@gmail.com changed:

   What|Removed |Added

 CC||aux...@gmail.com

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2020-10-23 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=406917

Kevin Funk  changed:

   What|Removed |Added

 CC||kf...@kde.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2020-04-02 Thread tjbp
https://bugs.kde.org/show_bug.cgi?id=406917

tjbp  changed:

   What|Removed |Added

 CC||kde@tjbp.net

--- Comment #17 from tjbp  ---
Possibly now fixed - see comment:
https://bugs.kde.org/show_bug.cgi?id=418910#c1

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2020-03-16 Thread Rigo Wenning
https://bugs.kde.org/show_bug.cgi?id=406917

--- Comment #16 from Rigo Wenning  ---
(In reply to csabi from comment #13)
If you can see the event in other calendars (I can see them on nextcloud web
and my Jolla Phone), but not in korganizer, I suspect, this has to do with
another bug (I don't have the number anymore) If you have imported the event
from an invitation letter and not "accepted" the invite in korganizer. The
event is in the calendar, but will not be shown in korganizer. You need to
accept it again in korganizer and it will show up.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2020-03-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406917

ad1r...@hotmail.fr changed:

   What|Removed |Added

 CC||ad1r...@hotmail.fr

--- Comment #15 from ad1r...@hotmail.fr ---
https://bugs.kde.org/show_bug.cgi?id=418910

oups i have created duplicate

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2019-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406917

xors...@gmx.net changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #14 from xors...@gmx.net ---
*** This bug has been confirmed by popular vote. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2019-10-07 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406917

--- Comment #13 from cs...@bxabi.com ---
Completely agreed, we an error message and ignoring the problematic event is
needed, not silently crash the calendar.

I was able to recover using the akonadi console, copying the events which were
not synced - no remote id - to a new calendar, then back to the original
calendar.
And couple restarts. They did get a new remote id after that.

BEGIN:VCALENDAR
PRODID:-//K Desktop Environment//NONSGML libkcal 4.3//EN
VERSION:2.0
X-KDE-ICAL-IMPLEMENTATION-VERSION:1.0
BEGIN:VEVENT
DTSTAMP:20191002T075812Z
URL:https:
 //www.eventbrite.com/e/codecontrol-community-meetup-7-storytelling-drinks-
 tickets-74687007851
CREATED:20191002T075812Z
LAST-MODIFIED:20191002T075812Z
DESCRIPTION:For details\, click here: https:
 //www.eventbrite.com/e/codecontrol-community-meetup-7-storytelling-drinks-
 tickets-74687007851
SUMMARY:CodeControl Community Meetup #7  (Storytelling & Drinks)
LOCATION:KollwitzstraÃe 91 - KollwitzstraÃe 91 - 10435 Berlin - 
 Germany
DTSTART;TZID=UTC:20191010T163000
DTEND;TZID=UTC:20191010T19
TRANSP:OPAQUE
END:VEVENT

END:VCALENDAR


Now I have all events working, saved in Nextcloud. So not sure it was a parsing
problem.

But: I have 2 events with empty UID's, and they don't show up in KOrganizer.
But they show up in Nextcloud and on my phone.
They were added through KOrganizer.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2019-09-25 Thread MartinG
https://bugs.kde.org/show_bug.cgi?id=406917

--- Comment #12 from MartinG  ---
I checked mine today, and mine is also back in none-sync mode. The sad thing
is, that I have put in a number of events in Korganizer, that are now not shown
in my shared Nextcloud calendar. I guess I will have to reset the connection
and lose all of those. I tend to import flight events into my calendar, and
those are often not fully sanitized. I'd much rather be confronted with an
error when this happens, with an option to ignore and move on, rather than to
be left in "offline mode" without knowing it!

Please let me know if any more info is needed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2019-09-19 Thread Rigo Wenning
https://bugs.kde.org/show_bug.cgi?id=406917

--- Comment #11 from Rigo Wenning  ---
Yes, my calendar is back in the no-sync status and entries are only within
akonadi and not synced to disk or nextcloud. I think this is a serious bug as
the algorithm as no plan B if it can't parse an entry.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2019-09-19 Thread Tim Schlotfeldt
https://bugs.kde.org/show_bug.cgi?id=406917

Tim Schlotfeldt  changed:

   What|Removed |Added

 CC||ts+...@ml.tschlotfeldt.de

--- Comment #10 from Tim Schlotfeldt  ---
I can confirm this. In run often into this while copying contact data (eg vcf
files) from one carddav ressource to another.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2019-07-09 Thread Rigo Wenning
https://bugs.kde.org/show_bug.cgi?id=406917

--- Comment #9 from Rigo Wenning  ---
I found the culprit. It was an ICS from Air Lingus that wasn't parsable. I
removed it from the calendar and now it works again. Looks like there is an
algorithm missing in the davgroup that throws away stuff that it can't digest
and notify the user. This should be coordinatable with the folks from nextcloud
as most people using kontact typically also use owncloud or nextcloud (as
google has certainly done the sanitization already)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2019-07-09 Thread Rigo Wenning
https://bugs.kde.org/show_bug.cgi?id=406917

--- Comment #8 from Rigo Wenning  ---
To unstuck mine, I had to remove and re-create the resource. Clearing was not
enough anymore as it seems akonadi remembered to fetch this non-existent item
despite clearing the cache and restarting the server.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2019-07-09 Thread Rigo Wenning
https://bugs.kde.org/show_bug.cgi?id=406917

Rigo Wenning  changed:

   What|Removed |Added

 CC||r...@w3.org

--- Comment #7 from Rigo Wenning  ---
Confirmation from here. I cleared the cache and now I have no items and no sync
anymore. Because clearing the cache did not do the trick anymore. I also had a
regression on this here:
https://www.dvratil.cz/2017/01/kmail-multiple-merge-candidates-error-and-how-to-fix-it/
I identified that the error wasn't in caldav, but in personal contacts and this
also stopped the caldav sync

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2019-07-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406917

--- Comment #6 from cs...@bxabi.com ---
Thank you.
The clash clearing did unstuck the calendar, so it can be used again (but
removed a few events which were not saved to the server).

This bug is particularly problematic because the calendar doesn't show any sign
that it stopped synchronizing. So on the computer everything looks fine, the
problem is detected when the calendar is checked on another device.

It would be good to get a notification when the calendar is stuck for some
reason.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2019-07-05 Thread heimlicher
https://bugs.kde.org/show_bug.cgi?id=406917

--- Comment #5 from heimlicher  ---
(In reply to csabi from comment #4)
> Hi, I have the same issue, it tries to load an event which doesn't exist on
> the server, and crashes.
> 
> I don't have a "Clear akonadi cache" button in the akonadi console. Where is
> that?

Here is a screenshot that will help you find it: https://ibb.co/0DgmwzS

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2019-07-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406917

cs...@bxabi.com changed:

   What|Removed |Added

 CC||cs...@bxabi.com

--- Comment #4 from cs...@bxabi.com ---
Hi, I have the same issue, it tries to load an event which doesn't exist on the
server, and crashes.

I don't have a "Clear akonadi cache" button in the akonadi console. Where is
that?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2019-05-07 Thread heimlicher
https://bugs.kde.org/show_bug.cgi?id=406917

--- Comment #3 from heimlicher  ---
After hitting  “Clear Akonadi Cache” in akonadiconsole the error disappeared.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2019-05-07 Thread heimlicher
https://bugs.kde.org/show_bug.cgi?id=406917

heimlicher  changed:

   What|Removed |Added

 CC||bugs.kde.org@openweb-berlin
   ||.de

--- Comment #2 from heimlicher  ---
I can confirm the above issue.
Trying to sync to my baikal server fails with a similar error.

akonadictl restart output:

parse error from icalcomponent_new_from_string. string= "\nhttp://sabredav.org/ns\;>\n 
3.1.3\n 
Sabre\\DAV\\Exception\\NotFound\n 
Calendar object not found\n\n"

org.kde.pim.davresource: DavGroupwareResource::onItemFetched: Failed to parse
item data.  "https://x/dav.php/calendars/c/2/1557222588.R271.ics;

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever

2019-04-26 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=406917

Christophe Giboudeaux  changed:

   What|Removed |Added

   Severity|major   |normal

--- Comment #1 from Christophe Giboudeaux  ---
I tested yesterday with demo.owncloud.com, I didn't get any issue.

I also have no issue with my regular caldav/carddav server

-- 
You are receiving this mail because:
You are the assignee for the bug.