Evolution Data Providers freezing process
- From: Neil Loknath <neil loknath gmail com>
- To: conduit-list gnome org
- Subject: Evolution Data Providers freezing process
- Date: Mon, 2 Feb 2009 00:15:51 -0700
I am running Conduit 0.3.15 on Ubuntu 8.10. Kernel 2.6.27-11. Evolution version is 2.24.3.
Adding any of an Evolution Contacts, Tasks, or Calender data source (those are the ones I've tried) and attempting to do a refresh result in Conduit freezing. Therefore, doing a sync results in the same thing. The process has to be killed.
This can be found in .xsession-errors:
[Conduit ][DEBUG ] Adding twoway dataprovider into source position (Conduit.py:140)[Syncronization ][DEBUG ] Created thread <RefreshDataProviderWorker(Thread-4, initial)> (thread: -1209861952) (Synchronization.py:211)
[Syncronization ][INFO ] Setting global cancel flag (Synchronization.py:90)[Syncronization ][DEBUG ] Starting worker: <RefreshDataProviderWorker(Wrapper: Evolution Tasks twoway (UID: EvoTasksTwoWay-default), initial)> (Synchronization.py:93)
[Syncronization ][DEBUG ] Started thread <RefreshDataProviderWorker(Wrapper: Evolution Tasks twoway (UID: EvoTasksTwoWay-default), started)> (thread: -1251980400) (Synchronization.py:814)
[Syncronization ][DEBUG ] Refresh <RefreshDataProviderWorker(Wrapper: Evolution Tasks twoway (UID: EvoTasksTwoWay-default), started)> beginning (Synchronization.py:816)
** (conduit:15310): DEBUG: Opening calendar source uri: defaultI am missing something? Or, should I bugzilla this?
Neil
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]