GNOME Bugzilla – Bug 563203
proxy autoconfig does not work
Last modified: 2009-11-30 16:45:24 UTC
Please describe the problem: This is related to bug 492076, but slightly different. In our company we have auto proxy config which is typically used. That has worked for years with 99% of applications. But Epiphany seems to block at least gtalk. Steps to reproduce: 1. configure gtalk account 2. enable gnome preferences -> network proxy -> automatic proxy connection 3. enable gtalk account -> no connect 4. change gnome preferences -> network proxy -> manual proxy conf -> gtalk becomes available 5. change back to autoconf of proxy -> gtalk drops Actual results: you can drop the gtalk connection by changing proxy to autoconf Expected results: it should be able to parse the autoconf Does this happen every time? yes Other information: this is common with many linux programs. Os is Fedora 10.
forgot to mention, that between the steps 4 and 5 you need to disable and re-enable gtalk from accounts. Empathy does not sniff the gnome proxy settings change.
Confirming this bug for now as Empathy should certainly do a better job in proxy management but MC is probably guilty as well.
ikke, you're probably on a more modern version of GNOME and of Empathy now. Could you check whether this problem is still happening?
Still the same bug exists: $ rpm -qf /usr/bin/gnome-network-properties control-center-2.26.0-10.fc11.x86_64 $ rpm -qa telepathy* telepathy-filesystem-0.0.1-3.fc11.noarch telepathy-haze-0.3.1-1.fc11.x86_64 telepathy-stream-engine-0.5.8-1.fc11.x86_64 telepathy-glib-0.7.29-1.fc11.x86_64 telepathy-salut-0.3.9-1.fc11.x86_64 telepathy-gabble-0.7.26-3.fc11.x86_64 telepathy-idle-0.1.3-2.fc11.x86_64 telepathy-farsight-0.0.6-1.fc11.x86_64 telepathy-mission-control-4.67-3.fc11.x86_64 telepathy-sofiasip-0.5.15-2.fc11.x86_64 $ rpm -q empathy empathy-2.26.2-1.fc11.x86_64
Empathy basically doesn't support any kind of proxy atm. Closing this bug as a dup of bug #602824 for now. We'll reconsider specific case once we'll have generic proxy support working. *** This bug has been marked as a duplicate of bug 547251 ***
*** This bug has been marked as a duplicate of bug 602824 ***