sync of groupdav contacts fails with "unknown error code 0"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KDE PIM |
Fix Released
|
Medium
|
|||
kdepim (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Precise |
Won't Fix
|
High
|
Unassigned |
Bug Description
a notification from akonadi indicates an error each time a sync of owncloud is intended (which is pretty annoying): "unknown error code 0".
there is an upstream bug: https:/
this is happening for the sync of contacts and there is a fix for it (it seems a kdepim patch is causing the issues and reversing it solves the problem, please see comments starting from #5), although in my opinion it didn't get enough attention and it's not fixed yet in current version of kdepim.
So the workaround turns out to be great for people that compiles kdepim but not for kubuntu users. I would be very grateful if kubuntu maintainers could push the fix upstream (apparently it would take few minutes to solve the issue). In the meantime, it would be great if a modified version of kdepim was in launchpad for the people that has this problem.
thanks
Changed in kdepim: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
Changed in kdepim (Ubuntu Precise): | |
importance: | Undecided → High |
Changed in kdepim (Ubuntu): | |
importance: | Undecided → High |
Changed in kdepim (Ubuntu Precise): | |
status: | New → In Progress |
every 5 minutes or so I get a popup from akonadi telling me that syncing from my owncloud calendar failed with "unknown error code 0".
Guys... return code 0 means "it worked fine", not "something went wrong"...
I looked at the debugger output in akonadiconsole, and there are no errors showing.
prior to upgrading to kde 4.8.3 everything worked.
Reproducible: Always
Steps to Reproduce:
1. use akonadi with owncloud calendars