Comment 6 for bug 1228154

Revision history for this message
reye (rtestacct) wrote :

I run into this issue at least every day or so. I don't normally reboot my computer unless it is needed but through my troubleshooting this issue below is the behavior I have experienced.

When I first boot the computer (Ubuntu 14.04 64bit) and run evolution 3.10.4 using evolution-ews I am prompted for my password once. After that point it appears to be a random time until I am prompted for my password again, sometimes it won't be until the next day, sometimes a few hours later. If I enter my password (correctly) I am prompted that my password was incorrect and to re-enter it. Trying this a couple different times has not produced a different result.

All available patches have been installed. I typically install any patches when they become available.

On the back end:
The Exchange servers that I am connecting to are running Exchange 2010 SP3 RU4. I do have an Exchange 2013 CU 6 server that I just finished installing. I will try some tests pointing to that server to see if I notice any different behavior.

Mitigation steps:
I have tried a couple different things. So far the only one that seems to make a difference is reducing the "Check for New Mail every" to 1 minute (Edit > Preferences > Mail Accounts > [Account Name] > Click Edit button > Receiving Options).
This seems to add a day or so until I get prompted again.

Workaround steps:
I have found that when I start getting the password prompt that simply closing Evolution and re-opening doesn't cause the issue to go away. What I have found that seems to help hold it off for a while longer without having to reboot my computer is to follow the steps below:

1. Close Evolution and all child windows
2. Open Terminal
3. run the current process command and grep to search for any remaining evolution processes. for example:
     sudo ps aux | grep -i evolution
4. if prompted enter your workstation password
5. get the process ID for any remaining evolution process (usually there are 3 processes), the process ID is typically in the second column. 1917, 2018, and 2196 in the sample below.

    username 1917 0.0 1.6 1601936 30324 ? SLl 08:45 0:00 /usr/lib/evolution/evolution-source-registry
    username 2018 0.0 4.2 1682524 78880 ? Sl 08:45 0:00 /usr/lib/evolution/evolution-calendar-factory
    username 2196 0.0 1.6 915272 30928 ? Sl 08:46 0:00 /usr/lib/evolution/3.10/evolution-alarm-notify

6. To stop the processes run the kill command with -9 with each process ID separated by a space, for example:
     sudo kill -9 1917 2018 2196
7. if prompted enter your workstation password.
8. Restart Evolution.

Next troubleshooting steps:
Test by killing only one of the remaining processes at a time to see if the issue is related to only one or more.
Test with Exchange 2013 CU6

If I missed any details that would be helpful please let me know.

R E