** Changed in: gwibber
Status: In Progress = Fix Released
** Changed in: gwibber (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/658554
Title:
** Branch linked: lp:~ken-vandine/gwibber/libproxy-wip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/658554
Title:
Socks 4/5 proxies not working with Gwibber
To manage notifications about this bug
** Changed in: gwibber (Ubuntu)
Importance: Undecided = Medium
** Changed in: gwibber (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/658554
Title:
** Also affects: gwibber (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/658554
Title:
Socks 4/5 proxies not working with Gwibber
--
ubuntu-bugs
This problem still occurs with the current gwibber PPA. The patch seems
reasonable, even if I don't see why the check wouldn't match the full
scheme syntax (i.e. socks://) just in case someone has a non-socks
proxy called socks.domain.tld.
$ apt-cache policy gwibber
gwibber:
Installé :
I think the problem now is that WebKit isn't adhering to the proxy
settings, even if Gwibber is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/658554
Title:
Socks 4/5 proxies not working with
