On Mon, 2010-02-22 at 11:32 -0500, Reid Thompson wrote: > On Mon, 2010-02-22 at 11:24 -0500, Reid Thompson wrote: > > On Mon, 2010-02-22 at 16:35 +0100, Milan Crha wrote: > > > On Mon, 2010-02-22 at 09:01 -0500, Reid Thompson wrote: > > > > OK, easy enough - WARNING **: LDAP authentication failed (0xffffffff > > > > (Can't contact LDAP server)) > > > > Can I turn on debug prints somewhere that will trace this connection > > > > attempt? > > > > > > Hi. > > > Interesting, it seems like it's trying to open your GAL in an > > > e-calendar-factory, which doesn't make much sense, as it should be > > > opened only in e-addressbook-factory, and shouldn't have any impact on > > > calendar itself. But who knows. > > > > > > If you've eex compiled with E2K_DEBUG, then try to run > > > e-calendar-factory with E2K_DEBUG=4 environment variable or higher, to > > > see communication with a server. > > > Bye, > > > Milan > > > > > > _______________________________________________ > > > Evolution-list mailing list > > > Evolution-list@gnome.org > > > http://mail.gnome.org/mailman/listinfo/evolution-list > > > > This is running get head as of friday. > > > > yes, whenever I select an ICS email, e-calendar-factory attempts to > > connect to whatever host is defined in preferences Global Catalog > > Server. > > > > ** (e-calendar-factory:30254): WARNING **: LDAP authentication failed > > (0xffffffff (Can't contact LDAP server)) > > > > I also get this error everytime I select an ICS email. > > > > (e-calendar-factory:30254): libecalbackendweather-CRITICAL **: > > e_cal_backend_weather_get_object: assertion `comp != NULL' failed > > > > Sometimes it appears that this causes e-calendar-factory to exit: > > > > > > ** (e-calendar-factory:30254): WARNING **: LDAP authentication failed > > (0xffffffff (Can't contact LDAP server)) > > (e-calendar-factory:30254): > > libexchangemapi-DEBUG: > > ../../../../evolution-mapi/src/libexchangemapi/exchange-mapi-connection.c:189: > > exchange_mapi_connection_new: lock(connect_lock) > > > > (e-calendar-factory:30254): libecalbackendweather-CRITICAL **: > > e_cal_backend_weather_get_object: assertion `comp != NULL' failed > > > > (e-calendar-factory:30254): libecalbackendweather-CRITICAL **: > > e_cal_backend_weather_get_object: assertion `comp != NULL' failed > > > > (e-calendar-factory:30254): libecalbackendweather-CRITICAL **: > > e_cal_backend_weather_get_object: assertion `comp != NULL' failed > > > > (e-calendar-factory:30254): libecalbackendweather-CRITICAL **: > > e_cal_backend_weather_get_object: assertion `comp != NULL' failed > > Bye. > > > > When it's 'not working' i get this... > > (evolution:30946): libecal-WARNING **: Cannot get cal from factory: No > backend factory for 'mapi' of 'VEVENT' > > (evolution:30946): libecal-WARNING **: Cannot get cal from factory: No > backend factory for 'mapi' of 'VEVENT' > > but there is a calendar factory running > > $ ps -ef|grep factory > rthompso 31005 1 0 11:25 ? 00:00:01 > /opt/evo/libexec/e-calendar-factory > rthompso 31029 1 0 11:25 ? 00:00:00 > /opt/evo/libexec/e-addressbook-factory > rthompso 31359 31300 0 11:27 pts/7 00:00:00 grep --colour=auto factory > > > If i kill the running one - evo pops up errors about calendar et al not being > available til restart.. > clicking on an ICS email causes another e-calendar-factory to be started, but > still 'not working' > > If I kill the running one and start one manually via > /opt/evo/bin/evolution-env /opt/evo/libexec/e-calendar-factory > then I get > ** (e-calendar-factory:31855): WARNING **: LDAP authentication failed > (0xffffffff (Can't contact LDAP server)) > (e-calendar-factory:31855): libexchangemapi-DEBUG: > ../../../../evolution-mapi/src/libexchangemapi/exchange-mapi-connection.c:189: > exchange_mapi_connection_new: lock(connect_lock) > > (e-calendar-factory:31855): libecalbackendweather-CRITICAL **: > e_cal_backend_weather_get_object: assertion `comp != NULL' failed > > But it 'works' > > I wonder if something is being set by /opt/evo/bin/evolution-env that is not > getting passed from evolution when it invokes > /opt/evo/libexec/e-calendar-factory?? > >
OK - resolved i guess... but not sure why this isn't being passed to /opt/evo/libexec/e-calendar-factory by evolutions invocation of /opt/evo/libexec/e-calendar-factory /opt/evo/bin/evolution-env exports LD_LIBRARY_PATH=/opt/evo/lib:$LD_LIBRARY_PATH Running manually /opt/evo/libexec/e-calendar-factory instead of /opt/evo/bin/evolution-env /opt/evo/libexec/e-calendar-factory gives the following output(and ics calendar does not work) (e-calendar-factory:3129): e-data-server-WARNING **: libldb.so.0: cannot open shared object file: No such file or directory Server is up and running... ** (e-calendar-factory:3129): WARNING **: LDAP authentication failed (0xffffffff (Can't contact LDAP server)) (e-calendar-factory:3129): libecalbackendweather-CRITICAL **: e_cal_backend_weather_get_object: assertion `comp != NULL' failed But then.... Manually setting export LD_LIBRARY_PATH=/opt/evo/lib:$LD_LIBRARY_PATH and running just /opt/evo/libexec/e-calendar-factory results in ics calendar working. _______________________________________________ Evolution-list mailing list Evolution-list@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-list
