gnome-network-preferences don't set $https_proxy,$ftp_proxy

Bug #95939 reported by Oliver
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNOME Terminal
Fix Released
Wishlist
apt (Ubuntu)
Invalid
Undecided
Unassigned
gnome-control-center (Ubuntu)
Invalid
Low
Unassigned
gnome-terminal (Ubuntu)
Fix Released
Wishlist
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-system-tools

Hi I'm running Edgy,
if i setup the proxy sever in gnome-network-preferences for http,https and ftp
only $http_proxy and $no_proxy are set.

thx Oliver

Revision history for this message
Sebastien Bacher (seb128) wrote :

not an apt bug

Changed in apt:
status: Unconfirmed → Rejected
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=425430

Changed in gnome-system-tools:
assignee: nobody → desktop-bugs
importance: Undecided → Wishlist
status: Unconfirmed → Confirmed
Changed in gnome-terminal:
status: Unknown → Unconfirmed
Revision history for this message
Hans Deragon (deragon) wrote :

Is this a dup of bug #48294?

Changed in gnome-terminal:
status: Confirmed → Triaged
Revision history for this message
Davide P. (scaltro) wrote :

I have the same terrible bug on my last patched gutsy.
When I unset global proxy through gnome-network-preferences, the http_proxy & ftp_proxy & https_proxy variable has the same previous assigned values. Perhaps the apps says that they are unassigned.
And so I have to force the cleaning of these values with
sudo export $http_proxy=
sudo export $ftp_proxy=
sudo export $https_proxy=

With gnome-network-preferences I can assign new proxy settings, but I cannot unset it.

Changed in gnome-control-center (Ubuntu):
importance: Undecided → Low
status: New → Invalid
Revision history for this message
Davide P. (scaltro) wrote :

gnome-network-preferences is part of gnome-control-center package... Why it should be declared invalid?
I think that the correct project to assign it is gnome-control-center.
I don't understand the low priority assigned.
This bug born in the 2007, Now on my last patched INTREPID 8.10, I got the same problem too.
In my first post I do a mistake when I wrote that my version of ubuntu was gutsy, instead it is the last intrepid one.

Changed in gnome-control-center:
status: Invalid → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

the gnome-control-center capplet only set gconf keys if those are not used by applications that's not a g-c-c bug

Changed in gnome-control-center (Ubuntu):
status: New → Invalid
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Upstream bug has been marked as duplicate of bug https://bugzilla.gnome.org/show_bug.cgi?id=596688

Changed in gnome-terminal:
status: New → Unknown
Changed in gnome-terminal:
status: Unknown → Fix Released
Changed in gnome-terminal:
importance: Unknown → Wishlist
Revision history for this message
JC Hulce (soaringsky) wrote :

The upstream fixed version has landed in Ubuntu.

Changed in gnome-terminal (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.