desktop-packages team mailing list archive

Thread
Date

[Bug 658554] Re: Socks 4/5 proxies not working with Gwibber

To: desktop-packages@xxxxxxxxxxxxxxxxxxx
From: Launchpad Bug Tracker <658554@xxxxxxxxxxxxxxxxxx>
Date: Thu, 15 Dec 2011 17:17:23 -0000
Reply-to: Bug 658554 <658554@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Branch linked: lp:~ken-vandine/gwibber/libproxy-wip

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gwibber in Ubuntu.
https://bugs.launchpad.net/bugs/658554

Title:
  Socks 4/5 proxies not working with Gwibber

Status in Gwibber:
  In Progress
Status in “gwibber” package in Ubuntu:
  Triaged

Bug description:
  Upon upgrade from Ubuntu 10.04 (official) to Ubuntu 10.10 (official),
  I noticed that I was getting nothing showing up in my Gwibber stream.
  I did a little investigation and found that I was getting the
  following output when running gwibber-service:

  -----------------------------------
  Traceback (most recent call last):
    File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line 57, in __init__
      self.curl.perform()
  error: (56, 'Proxy CONNECT aborted')
  -----------------------------------

  and this was in the log file:
  -----------------------------------
  2010-10-11 11:39:43,497 - Gwibber Dispatcher - ERROR - Failed to communicate with https://api.twitter.com/1<personal stuff>
  2010-10-11 11:39:43,499 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
  -----------------------------------

  I often use a SOCKS proxy via "ssh -D ..." and it appears that
  gwibber-service was failing to connect when I would use the proxy
  since it worked fine when I turned it off.  It appears that [py]curl
  is not correctly setting the correct proxy options with the proxy url
  that is being used, in my case "socks://localhost:50001".  On the plus
  side, this is an easy fix.  I simply set the PROXYTYPE opt to
  PROXYTYPE_SOCKS4 (it also works with PROXYTYPE_SOCKS5) and everything
  works perfectly, with my proxy.

  I've attached a small patch that addresses this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gwibber/+bug/658554/+subscriptions