On Sun, 23 May 2010 15:59:57 -0500, Jonathan wrote in message <20100523205957.ga15...@progeny.tock>:
> clone 582705 -1 > severity -1 minor > retitle -1 hard to debug incorrect proxy settings > tags -1 + upstream > quit > > Arnt Karlsen wrote: > > > ..I just found out "chromium-browser --no-proxy-server &" > > does exactly what I want it to, use my proxy servers blindly > > instead of trying to smart-ass itself around them. ;o) > > Ah, okay. At a glance, I see two things to do here: > > . Track down the null pointer dereference you mentioned. > > . Make the net::ERR_NAME_NOT_RESOLVED message (is that the one > you were getting?) mention the --proxy-server options when a > proxy is in use, to help with debugging. ..nope, I get "Error 324 (net::ERR_EMPTY_RESPONSE): Unknown error." on the first and 102's on the other lan boxes, motion web servers serving jpg's, not flash. Googling points upstream to Google. ;o) ..this is with today's updated 5.0.375.55~r47796-1, the old one's errors looked the same, AFAIR. > Cloning the bug. > > Thanks again, > Jonathan > -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
