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. Cloning the bug. Thanks again, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
