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: k
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 f
*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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Previous upstream report as a duplicate of this one
** Changed in: chromium-browser
Remote watch: code.google.com/p/chromium/issues #106052 =>
code.google.com/p/chromium/issues #123288
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/983777
Tit
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?i
Bug reported in Google bug database
http://code.google.com/p/chromium/issues/detail?id=106052&q=proxy%20kubuntu&colspec=ID%20Pri%20Mstone%20ReleaseBlock%20Area%20Feature%20Status%20Owner%20Summary
** Also affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Bug watc
