GNOME Bugzilla – Bug 561095
Evolution Memos
Last modified: 2009-02-13 11:32:12 UTC
Please describe the problem: Evolution memos to folder (or anything else ) is not working Steps to reproduce: 1. Launch conduit 2. make a connexion between Evolution memos to a folder 3. Synchronish group Actual results: [Syncronization ][DEBUG ] Created thread <SyncWorker(Thread-5, initial)> (thread: 1875998400) (Synchronization.py:211) [Syncronization ][INFO ] Setting global cancel flag (Synchronization.py:90) [Syncronization ][DEBUG ] Starting worker: <SyncWorker(Wrapper: Evolution Memos twoway (UID: EvoMemoTwoWay-) |--> [<conduit.ModuleWrapper.ModuleWrapper instance at 0x932626c>], initial)> (Synchronization.py:93) [Syncronization ][DEBUG ] Started thread <SyncWorker(Wrapper: Evolution Memos twoway (UID: EvoMemoTwoWay-) |--> [<conduit.ModuleWrapper.ModuleWrapper instance at 0x932626c>], started)> (thread: 1774033808) (Synchronization.py:624) [Syncronization ][DEBUG ] Sync <SyncWorker(Wrapper: Evolution Memos twoway (UID: EvoMemoTwoWay-) |--> [<conduit.ModuleWrapper.ModuleWrapper instance at 0x932626c>], started)> beginning. Slow: False, Twoway: False (Synchronization.py:629) [Syncronization ][DEBUG ] Syncworker state 0 (Synchronization.py:648) [Syncronization ][DEBUG ] Syncworker state 1 (Synchronization.py:648) [Syncronization ][DEBUG ] Source Status = Error Refreshing (Synchronization.py:677) ** (conduit.real:3388): DEBUG: Opening calendar source uri: ** (conduit.real:3388): WARNING **: Unable to find source for calendar (type 2) [Syncronization ][CRITICAL] UNKNOWN REFRESH ERROR: Wrapper: Evolution Memos twoway (UID: EvoMemoTwoWay-) Traceback (most recent call last):
+ Trace 209887
self.source.module.refresh()
for i in self.memos.get_all_objects():
(Synchronization.py:688) Expected results: Does this happen every time? Yes Other information: Unable to find source for calendar for Memos ?
The evo code for contacts, cal and memos is almost identical. Its the same problem *** This bug has been marked as a duplicate of 561090 ***