Socks 4/5 proxies not working with Gwibber
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gwibber |
Fix Released
|
Undecided
|
Michael Hall | ||
gwibber (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
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/
self.
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:/
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:
I've attached a small patch that addresses this issue.
Related branches
- Robert Bruce Park: Disapprove
- gwibber-committers: Pending requested
-
Diff: 12 lines (+2/-0)1 file modifiedgwibber/microblog/network.py (+2/-0)
Changed in gwibber: | |
status: | New → In Progress |
assignee: | nobody → Michael Hall (mhall119) |
Changed in gwibber (Ubuntu): | |
importance: | Undecided → Medium |
status: | Confirmed → Triaged |
Changed in gwibber: | |
status: | In Progress → Fix Released |
Changed in gwibber (Ubuntu): | |
status: | Triaged → Fix Released |
I can confirm both the bug and the apparent correctness of the patch. I just applied the patch to my /usr/share/ pyshared/ gwibber/ microblog/ network. py (current Maverick) and now my Gwibber finally updates through the SOCKS proxy again.
Thanks for the patch!