After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 549823 - $http_proxy not set in nautilus-scripts
$http_proxy not set in nautilus-scripts
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: Scripts facilities
2.22.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-29 14:07 UTC by rom
Modified: 2021-06-18 15:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description rom 2008-08-29 14:07:02 UTC
Please describe the problem:
When I launch a script from a console, $http_proxy has the value entered in gnome proxy.

If I launch exactly the same script in nautilus (a nautilus script), $http_proxy is empty (so my script doesn't work, it needs to access internet).

Steps to reproduce:
1. set a proxy in gnome
2. create a script with a line zenity --info --text "proxy=$http_proxy" in ~/.gnome2/nautilus-scripts
3. launch it from gnome-terminal
4. launch it from nautilus


Actual results:
$http_proxy is empty when launched from nautilus

Expected results:
it should be set

Does this happen every time?
yes

Other information:
Comment 1 Cosimo Cecchi 2008-08-30 10:32:34 UTC
It seems that if you restart Nautilus, it works just fine. Don't know what we should do here.
Comment 2 rom 2008-09-01 08:07:52 UTC
I don't know, but some programs are aware of a change in gnome proxy settings.
For example, pidgin, firefox, or weather applet : no need to restart them after a change in proxy settings.
Comment 3 André Klapper 2021-06-18 15:13:55 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version of Files (nautilus), then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/

Thank you for your understanding and your help.