Re: Evolution Data Providers freezing process

[Neil Loknath <neil loknath gmail com>]

Thanks!  I guess I searched for the wrong word in bugzilla.  Freeze = lock up.

On Mon, Feb 2, 2009 at 10:50 AM, Julien Lavergne <julien lavergne gmail com> wrote:

Seems to be this bug : http://bugzilla.gnome.org/show_bug.cgi?id=561354

Regards,
Julien Lavergne

On Mon, 2009-02-02 at 00:15 -0700, Neil Loknath wrote:
> 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: default
>
> I am missing something?  Or, should I bugzilla this?
>
> Neil

> _______________________________________________
> Conduit-list mailing list
> Conduit-list gnome org
> http://mail.gnome.org/mailman/listinfo/conduit-list