Bug 731807

Thanks for a bug report. Is it the only error it prints on the console, please? I'm interested in the output before it, as anything after this can be cause by it.

I'm wondering what this can be, because I vaguely recall similar issue being fixed months ago, there it was about accessing already freed memory. Could you try to run evolution under valgrind, to see whether it'll show anything, please? You can do that with command like this (with 'valgrind' package installed):
   $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>log.txt
And if it'll not work, the exchange account will not be functional, then close evolution and attach here the log.txt file. Check its content for any private information you would not like to share, though valgrind logs do not expose user names, passwords or server names usually. Please note that running evolution under valgrind also means a significantly slower processing due to all memory checking, thus give it some time till it runs and till it does all the tasks it does on start.

Created attachment 519050 [details]
Valgrind's log of evolution execution

Hi!
Thanks for answer to my bug report. I'm attaching the valgrind's log for the evolution execution.

Yeah, same here. Maybe some update caused it to start failing. Not sure.

Just for kicks, tried MAPI support, which I haven't tried for a long time now. Unfortunately, still unusable with a large mailbox, over many folders, like mine. Just FYI.

Thanks for the update. The valgrind log shows all the warnings as you wrote above, but valgrind itself doesn't find an issue with it, thus it seems like it's cased by something else than a used memory after free.

It might be checkable whether Bojan has right with the update, especially if it's caused by an update to evolution-exchange. You can go to a previous version of it by running a command like this:
   $ yum downgrade evolution-exchange
to test whether any latest update to it causes an issue, though I do not see any change directly related to this between 3.0.0 and current 3.0.2. The other option is libsoup, which evolution-exchange is using to communicate with the server.

I also tried with current Fedora 15 (after yum update), and I do not see such issue with evolution-exchange, it behaves correctly here. I only noticed that

> LDAP authentication failed (0xffffffff (Can't contact LDAP server))

warning on the console, but only for the first time, when I enabled the exchange account. Could you try to disable the exchange account, close evolution, run evolution, go to Mail Accounts preferences, edit the exchange account, re-authenticate and then enable it, please? Maybe something broke with the configuration? I'm pretty out of idea here, right now.

I recreated the account several times. It's not the config, I think.

BTW, it just stopped working for me, out of the blue. I'll downgrade evolution-exchange and verify again.

Downgraded to 3.0.1-1.fc15, configure the account and I can see my e-mail again. OK, let me upgrade again...

Upgraded, still works. Confused, to be honest.

Hrm, I'm confused too. The only explanation I can think of is that the locally stored data were corrupted in some way, which prevented evolution-exchange behave properly. Removing the account and configure it again doesn't remove this stored data, and because you've it stored in the same folder in 3.0.x (the 3.2.x will store per account UID, thus this will not be true in that and later version), then these data could be reused. Whether previous version of evolution-exchange fixed any such hypothetical data brokenness is just a question.

If by data you mean stuff in ~/.local/share/evolution/mail/exchange/<account>, then no. I've blown this away many times after killing evo, addressbook and calendar processes. I also killed state.ini for mail several times.

Maybe I and the original reporter work for the same company without knowing and Exchange admins are screwing with us :-)

(In reply to comment #10)
> If by data you mean stuff in ~/.local/share/evolution/mail/exchange/<account>,
> then no. I've blown this away many times after killing evo, addressbook and
> calendar processes. I also killed state.ini for mail several times.

Yup, those data I mean. Note there are other in ~/.local/share/evolution/exchange, and for calendar and addressbook also in ~/.cache/evolution, but these might not play a role in the mailer.

> Maybe I and the original reporter work for the same company without knowing and
> Exchange admins are screwing with us :-)

Hehe, I like this explanation :)

(In reply to comment #7)
> Downgraded to 3.0.1-1.fc15, configure the account and I can see my e-mail
> again. OK, let me upgrade again...

Did you erase the account and create it again? or you just got authenticated again?

I downgrade evolution-exchange and it worked... This definitely is about the upgrade of evolution-exchange package...

(In reply to comment #12)
 
> Did you erase the account and create it again? or you just got authenticated
> again?

I did yes. But I see it worked for you even without doing that.

I checked changes done between 3.0.1 and 3.0.2 of evolution-exchange in Fedora 15 and there are done only these code changes from Gnome's bugzilla:
   Bug 648612 crash during drag & drop of recurring events
   Bug 436619 fix a small error
   Bug 339827 EDS crashes on startup
and they all are in calendar, the rest of evolution-exchange is unchanged. Bojan said, that updating back to 3.0.2 works again (I hope after restart too), thus this all seems just like a coincidence to me.

It happened again, the same problem and I didn't change anything. I downgrade  evoltuion-exchange when the problem got solved and I'm still on version 3.0.1, this is very weird...

This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping