chromium doesn't see system proxy config

Bug #983777 reported by Jeroen
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Chromium Browser
Incomplete
Unknown
Kubuntu PPA
Fix Released
Undecided
Unassigned
chromium-browser (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

The chromium browser only works when I pass my proxy settings using the proxy server parameter:
chromium-browser --proxy-server=http://localhost:3128

Other browsers (firefox, rekonq) just pick up my system wide browser settings.

This issue has been fixed before, https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/858252

google-chrome has the same problem.

Tags: 12.04 kubuntu
Revision history for this message
Andrew Simpson (andrew-simpson) wrote :

Confirmed in Kubuntu 12.04 release.

tags: added: 11.04 kubuntu
tags: added: 12.04
removed: 11.04
Revision history for this message
Andrew Simpson (andrew-simpson) wrote :
Revision history for this message
Andrew Simpson (andrew-simpson) wrote :

 Bug is caused when Kubuntu settings for system proxy are manually set in System Settings --> Network Settings --> Proxy --> Manually Specifiy the Proxy settings.

The cause and a workaround is given in comment #6 of the Google bug report.

See also KDE bug report https://bugs.kde.org/show_bug.cgi?id=288002

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
Revision history for this message
Maarten Bezemer (veger) wrote :

Thanks for taking the time to report this bug in the upstream bug tracking system this is a tremendous help. Launchpad has the ability to watch lots of upstream bug trackers and this can be done by following the procedure documented at https://wiki.ubuntu.com/Bugs/Watches. I've added the bug watch for this bug report.

Revision history for this message
Maarten Bezemer (veger) wrote :

Previous upstream report as a duplicate of this one

Revision history for this message
Jeroen (c0p3rn1c) wrote :

The error message has changed from "403" to "Error 111 (net::ERR_TUNNEL_CONNECTION_FAILED): Unknown error."

starting chromium with "chromium-browser --proxy-server=http://localhost:3128" still fixes this issue.

Revision history for this message
Jeroen (c0p3rn1c) wrote :

*Concerning my last message: "403" should be "Error 130 (net::ERR_PROXY_CONNECTION_FAILED): Proxy server connection failed."

It might have something tod o with the recent upgrade from squid2 to squid3.

Revision history for this message
Simon Quigley (tsimonq2) wrote :

Thank you for taking the time to report this bug and helping to make Kubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Kubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Kubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 983777

and any other logs that are relevant for this particular issue.

Changed in chromium-browser:
status: Unknown → Incomplete
Changed in kubuntu-ppa:
status: New → Incomplete
Changed in chromium-browser (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Paul White (paulw2u) wrote :

Upstream issue showing "Fixed" in May 2012
No reply to request for info in comment #9
Report did not expire due bug watch
No comments by those affected for nearly 7 years
So closing as being fixed

Changed in chromium-browser (Ubuntu):
status: Incomplete → Fix Released
Changed in kubuntu-ppa:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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