"error code from SyncEvolution fatal error (local, status 10500): no datastores active, check configuration"
Bug #1577416 reported by
Ken VanDine
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical System Image |
Fix Released
|
High
|
Bill Filler | ||
| sync-monitor (Ubuntu) |
Triaged
|
High
|
Renato Araujo Oliveira Filho | ||
Bug Description
I'm seeing this error when attempting to sync the calendar.:
"error code from SyncEvolution fatal error (local, status 10500): no datastores active, check configuration"
Perhaps it's related to this message:
"error" : "event not found"
Related branches
lp://staging/~renatofilho/qtorganizer5-eds/fix-1577416
- Arthur Mello (community): Approve
- Tiago Salem Herrmann (community): Approve
- PS Jenkins bot: Approve (continuous-integration)
-
Diff: 184 lines (+103/-17)3 files modifiedorganizer/qorganizer-eds-engine.cpp (+8/-3)
tests/unittest/eds-base-test.cpp (+14/-3)
tests/unittest/recurrence-test.cpp (+81/-11)
Revision history for this message
| Ken VanDine (ken-vandine) wrote | #1 |
| Changed in sync-monitor (Ubuntu): | |
| assignee: | nobody → Renato Araujo Oliveira Filho (renatofilho) |
| Changed in sync-monitor (Ubuntu): | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| importance: | Medium → High |
Revision history for this message
| Renato Araujo Oliveira Filho (renatofilho) wrote | #2 |
Revision history for this message
| Pat McGowan (pat-mcgowan) wrote | #3 |
| Changed in canonical-devices-system-image: | |
| assignee: | nobody → Bill Filler (bfiller) |
| importance: | Undecided → High |
| milestone: | none → 11 |
| status: | New → In Progress |
| Changed in canonical-devices-system-image: | |
| status: | In Progress → Fix Committed |
| Changed in canonical-devices-system-image: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I could not reproduce this specific error. But I was able to cause my sync to fail after edit a specific instance of a recurrent event. I believe they are related.
A initial fix is on this branch: https:/