Package Details: proxydriver 1.61-2

Git Clone URL: https://aur.archlinux.org/proxydriver.git (read-only)
Package Base: proxydriver
Description: Sets GNOME or KDE proxy settings using NetworkManager's informations
Upstream URL: http://marin.jb.free.fr/proxydriver/
Licenses: GPL
Submitter: None
Maintainer: marcs
Last Packager: marcs
Votes: 20
Popularity: 0.170228
First Submitted: 2011-02-07 11:03
Last Updated: 2015-06-13 14:01

Latest Comments

Georgo10 commented on 2016-05-20 12:47

In case you want working script, fetch this fork from github: https://github.com/j1ml/proxydriver

jaro3 commented on 2015-11-13 02:26

The script no longer works apparently because the nmcli command syntax has changed:

proxydriver[1386]: script called: enp6s0 up
proxydriver[1387]: interface 'enp6s0' now up, will try to setup proxy config
uration...
nm-dispatcher[1165]: Usage: nmcli connection { COMMAND | help }
nm-dispatcher[1165]: COMMAND := { show | up | down | add | modify | edit | d
elete | reload | load }
nm-dispatcher[1165]: show [--active] [[--show-secrets] [id | uuid | path | a
path] <ID>] ...
nm-dispatcher[1165]: up [[id | uuid | path] <ID>] [ifname <ifname>] [ap <BSSID>] [passwd-file <file with passwords>]
...
nm-dispatcher[1165]: Error: 'status' is not valid 'connection' command.

jaro3 commented on 2014-04-30 00:46

Doesn't work after recent OS updates :-(

nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/
99-proxydriver.sh' took too long; killing it.

NetworkManager: <warn> Dispatcher script timed out: Script '/etc
/NetworkManager/dispatcher.d/99-proxydriver.sh' timed out.

Tharre commented on 2013-10-04 11:00

You need to enable NetworkManager-dispatcher.service now as it was splitted up.

rafaelff commented on 2012-03-30 04:21

This software depends on 'gconf' when it calls 'gconf-tool-2' and 'kdebase-runtime' when call 'kwriteconfig'. You should add it at least as optdepends=() to warn the user about it.

Anonymous comment on 2012-02-21 16:57

Hi there, I've tried to set it up, with xhost +si...
When I boot it says in user.log that it found the correct wifi and uses the corresponding .conf for that ssid. But after that it also says that it's setting those configurations for 'unkown', where it should say my username.
If I then execute that exact command (xhost +si...), that I set up to be executed on boot, in a terminal and reconnect the wifi it uses my username instead of unkown.
So somehow it's not properly executing it on boot!

Any help?

Anonymous comment on 2011-02-10 20:49

In order for this to work, you need to execute this command, as part of the GNOME startup process (
System->Preferences->Startup Applications):

xhost +si:localuser:your_username