GNOME Bugzilla – Bug 670949
Evolution uses SOCKS4 proxy when proxy is turned off in preferences
Last modified: 2012-05-17 18:21:53 UTC
I upgraded to debian wheezy today, and in the process Evolution was upgraded to 3.2.2. In the process I switched away Gnome3 to another windows manager. After setting that up I ran Evolution for the first time and it refused to collect new emails. It variously complained about being disconnected, timeouts and occasionally the configured proxy not being a SOCKS4 proxy. Turned out it was going to our local http proxy for every connection, which of course refused to have anything to do with it. At the start Evolution preferences were set to use the system's proxy settings, but when I changed that to "Direct" it continued to happen. This is the bug. For what it was worth the System was _not_ configured to use a proxy in the .gconf settings. That Evolution was trying to use a SOCKS4 proxy in the face of this is another bug, but probably not in Evolution itself. It turned out it was reading the proxy setting from the file $HOME/.config/dconf/user. Removing that file fixed the problem. I suspect that file is normally updated by Gnome3, but as I said I had switched away from that earlier and instead was editing the .gconf settings using gconf-editor which is I gather a sanctioned way of editing Gnome3 settings. This second bug may be that gconf-editor doesn't update .config/dconf/user.
Thanks for a bug report. The Gnome applications are moving from GConf to GSettings, which is using dconf at the background, an din time of 3.2.x Gnome's proxy settings had been already moved to GSettings, while Evolution's proxy settings left in GConf. The is used dconf-editor to edit GSettings. Evolution's proxy uses GSettings values only when there is set to use System proxy, otherwise it doesn't read from that key. Or it at least should not. I checked the changes in the related file and I see that the SOCKS proxy is not used at all in evolution with 3.2.x, this had been added for 3.4.0 in bug #601898. With change from that bug it should start working as expected. I thinkI can mark this as a duplicate of that bug, what do you think?
> I think I can mark this as a duplicate of that bug, what do you think? It is a bit hard to for me to judge without spending some hours looking at the source code, but it sounds reasonable.
(In reply to comment #2) > > I think I can mark this as a duplicate of that bug, what do you think? > > It is a bit hard to for me to judge without spending some hours looking at the > source code, but it sounds reasonable. Yeah, similar for me, I didn't definitely ask you to review the code :) My point is that the 3.2.x doesn't use any proxy for SOCKS before the fix from bug #601898, thus the behaviour you see is fixed by properly listen and use those SOCKS/proxy settings also for mailer part of evolution. *** This bug has been marked as a duplicate of bug 601898 ***