Red Hat Bugzilla – Bug 844120
Evolution using EWS crashes when password is changed in seahorse
Last modified: 2013-07-31 23:45:28 EDT
Description of problem:
Most Exchange sites enforce periodic password change. If on such a password change one changes the stored password using seahorse while Evo is running (and while still being connected to Exchange over EWS) and after Evo reported that the password is wrong on mail refresh, Evo may crash.
Version-Release number of selected component (if applicable):
Once thus far.
Steps to Reproduce:
1. Change AD password, while connected to Exchange using EWS.
2. Change stored password using seahorse after Evo reports incorrect password on mail refresh.
3. Evo crashes after a while.
Should pick up the new password and continue.
Exchange server was also behaving a bit odd at the time. The crash may have been a result of some other back end failure. Unfortunaly, abrt did not catch anything.
Thanks for a bug report. I'm afraid without backtrace it'll be hard to find the right cause. I suggest to try a test package  which contains quite many fixes which will be part of evolution-ews-3.4.4, and I recall some similar crash being addressed there as well. The tests of the package show that this is less crashing than before.
If you want to get a backtrace without using ABRT, then you can run evolution under gdb (please install debuginfo packages for evolution-data-server, evolution and evolution-ews first, and make sure they will be of the same version as binary packages), and get a backrace. You can do it with command like this:
$ gdb evolution --ex r --ex "t a a bt" --ex q
Please let me know whether the test package helped. Thanks in advance.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is 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 change the
'version' to a later Fedora version prior to Fedora 17's end of life.
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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.