On Mon, 2011-03-28 at 10:42 +0200, Yves-Alexis Perez wrote: > On sam., 2011-03-19 at 23:05 -0400, Wendy Elmer wrote: > > I upgraded another machine to the 2.32 version of evolution. That > > upgrade went okay. > > I noticed that when I first started evolution that I could see the 0% > > statuses at the bottom > > and then a pop-up window came us asking me to verify the SSL > > certificate. I clicked okay and > > everything started up fine. > > > > On the machine that failed and hung on 0%, I remember thinking there > > might be a pop-up behind > > the window so I minimized the main window but I did not find a pop-up > > window. Maybe the problem > > was that there was a pop-up waiting for a response but the pop-up was > > not visible for some reason. > > It might be related to #616587 indeed, so it'd help to test with eds -4 > just to confirm/infirm that. > > Regards,
I upgraded evolution on two other machines without any problem. I upgraded on the machine that hung saying 0% complete on everything. On one user login on that machine evolution worked okay. On the other user login on that machine everything in evolution hung saying 0% complete. On every machine that I upgraded and user logins that worked, the first time I started evolution after the upgrade, I would get a popup asking to verify the SSL certificate. For the userid that kept failing, I tried to force evolution to prompt for the imap passord. So, I unchecked remember password in the settings, removed all keyrings, and shut down and restarted the computer. When I started evolution, it did not ask for the passord, evolution just hung saying 0% complete. I looked behind all windows to see if the popup was hidden. There was no popup. So, I started investigating the differences between the login that worked and the one that didn't. On that computer I run squid and squidguard so I go through the squid network proxy on the network preferences. I changed the network connection on the failing login to not go through the proxy and do a direct connection. When I started evolution after that, it prompted me for the password and then the mail loaded correctly. So, the problem with the 2.32 version of evolution is that prompting for SSL authorization or passwords does not work through the squid/squidgaurd proxy. Evolution just hangs without issuing a popup prompt yet won't continue until the non-existent prompt is answered. The previous evolution 2.30 version never had the problem. Once evolution gets the password or SSL authorization, going through the squid/squidguard proxy works fine for loading email. This was a particularly bad problem to have because upgrading to 2.32 from the previous testing version moves the ~/.evolution directory. So, when I downgraded to version 2.30 so evolution would work, all of my saved mail was lost because the upgrade wiped out the ~/.evolution directory. There should be something in the README or something warning about backing down to a previous version after 2.32 has been installed. So, I see two problems: 1. evolution 2.32 does not issue prompts when going through squid/squidguard which is a regression from 2.30 2. there should be a warning somewhere about downgrading from 2.32 and the moving of the .evolution directory Brent
