Regression: "Automatic proxy configuration" + gnome-terminal now breaks apt-get, curl, wget...
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libsoup |
Fix Released
|
Medium
|
|||
apt (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
curl (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
gnome-terminal (Ubuntu) |
Invalid
|
Low
|
Unassigned | ||
libsoup2.4 (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
update-manager (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
wget (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: gnome-terminal
The fix for bug 48294 -- at least as implemented in gnome-terminal 2.27.92-0ubuntu1 from Karmic -- may be theoretically more correct, but it seems to have broken strictly more apps than it fixes.
Steps to reproduce:
1) Go to System -> Preferences -> Network Proxy, select "Automatic proxy configuration", and enter the URL of a PAC proxy (I use http://
2) Start a gnome-terminal.
3) echo $http_proxy
Before bug 48294 was fixed, this produced "http://
$ http_proxy=http://
$ http_proxy=http://
$ http_proxy=http://
With current gnome-terminal, the above steps result in http_proxy being set to "pac+http://
$ http_proxy=pac+http://
$ http_proxy=pac+http://
$ http_proxy=pac+http://
So not only did this "fix" fail to fix the old broken software, it breaks new software, and the newly broken software is failing in very confusing ways.
In the long run this should perhaps be considered a bug in wget, curl, apt-get, and every other HTTP implementation in in Ubuntu, but I'm filing against gnome-terminal because 1) that's what caused the regression, 2) at this point in the release cycle I'm guessing you might want to just unset http_proxy in these proxy auto-config cases (none of this software could parse the PAC file anyway, it requires a javascript interpreter), rather than try to fix everything everywhere...
Changed in gnome-terminal (Ubuntu): | |
importance: | Undecided → Low |
Changed in libsoup2.4 (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in gnome-terminal (Ubuntu): | |
status: | New → Confirmed |
Changed in libsoup: | |
status: | Unknown → Fix Released |
Changed in libsoup: | |
importance: | Unknown → Medium |
Actually, I'm sorry, it might not be gnome-terminal that has the offending code anymore -- this bug seems to affect apps launched from the panel, too.
In particular, update-manager is now broken. (I was *wondering* why it hadn't popped up since I upgraded...) The error message is uninformative, but I confirmed that it is the same problem by (1) verifying via /proc/$(pidof update- manager) /environ that update-manager had the bad http_proxy variable set, (2) turning off the proxy in Network Proxy Preferences, (3) restarting update-manager (4) confirming that the http_proxy environment variable was gone and that (5) update-manager now worked.
I think that may make this what Debian would call a "critical" bug.