package gpodder retitle 696117 gpodder: No useful information on failure to contact HTTP proxy thanks
On 21-Dec-2012, Ben Finney wrote: > There are *no* HTTP packets in the TCPDump capture during the gPodder > session. The only traffic captured at all is from my IRC client; gPodder > appears to have generated no traffic. Further investigation shows that this was because of a faulty ‘http_proxy’ environment variable value; the host name would not resolve. There was no traffic to indicate a DNS query from gPodder. The traceback gives no indication of this problem. The resulting message, of course, is also no help in diagnosing this. So this bug report becomes one drawing attention to gPodder's failure to provide sufficient information to indicate that it is unable to contact the HTTP proxy; please forward this to the relevant upstream bug tracker. -- \ “It's up to the masses to distribute [music] however they want | `\ … The laws don't matter at that point. People sharing music in | _o__) their bedrooms is the new radio.” —Neil Young, 2008-05-06 | Ben Finney <b...@benfinney.id.au>
signature.asc
Description: Digital signature
