Bug 165635 - www/chromium: 17.0.963.56: proxy isn't read by chrome from kde4
Summary: www/chromium: 17.0.963.56: proxy isn't read by chrome from kde4
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-02 20:10 UTC by yuri
Modified: 2014-09-04 07:05 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description yuri 2012-03-02 20:10:11 UTC 
"Change Proxy Settings" button brings up kde4 "Proxy - KDE Control 
Module" screen.
When I change to "Manually specify the proxy" and set the proxy for all 
protocols to 109.251.143.22 port 8080 abd hit Apply opening another 
google.com instance shows that proxy isn't used. With this proxy Google 
shows with "Ukraine" icon.

Not sure if this is FreeBSD specific or generic with kde4. But in chrome 
on Ubuntu proxy is read from gnome settings there.
Comment 1 Jason Helfman freebsd_committer freebsd_triage 2012-03-03 00:33:52 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->chromium

fix synopis and assign
Comment 2 Carlo Strub freebsd_committer freebsd_triage 2014-08-29 21:48:35 UTC 
back to pool
Comment 3 Carlo Strub freebsd_committer freebsd_triage 2014-09-03 19:03:09 UTC 
Is this PR still relevant?
Comment 4 Yuri Victorovich freebsd_committer freebsd_triage 2014-09-04 01:36:22 UTC 
Just close it.

There is a great add-on that manipulates proxies, overriding whatever functionality chrome has built-in, broken or not.
Comment 5 Carlo Strub freebsd_committer freebsd_triage 2014-09-04 07:05:13 UTC 
Closing.