Comment 11 for bug 15036

Revision history for this message
Russell Cok (ruscook-oz) wrote :

(In reply to comment #10)
> (In reply to comment #9)
> > Have re-run on a different machine this morning and when changing from mail to
> > calendar evolution has hung after the following message in the connector window.
>
> I assume this was a newly setup Evolution instance?
No this is my laptop (which exhibits the problem much worse than my home
desktop) - mainly I think because the laptop is on the LAN at work and the
desktop is only on ADSL at home.
>
> > GET /exchange/ruscook/Calendar/Updated: Financial System Performance.EML
HTTP/1.1
> > E2k-Debug: 0x86fe620 @ 1119219189
> > Host: mail.mcs.usyd.edu.au
> > Translate: F
> > User-Agent: Evolution/2.2.1.1
> >
> > Xlib: unexpected async reply (sequence 0x9e)!
>
> This is a new error, right? I might have a fix for that particular error,
> actually. It's on my work computer, I'll attach it to this bug tomorrow.
Possibly, I have had the data-server also lock/use all of available CPU up
before. I have some additional info on this bug from the debug screen:

attr = ou, info = 0xb7c0976c
value = people
attr = objectClass, info = (nil)
looked up msgid 4, got op 0x866be78

I hope this info helps as I'd really like Evolution to be stable with Exchange.
And thanks for working on this.
Russ