I'm getting a similar experience:
gwibber-service Updating... Traceback (most recent call last): File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line 32, in __init__ self.curl.perform() error: (7, "couldn't connect to host") Traceback (most recent call last): File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line 32, in __init__ self.curl.perform() error: (7, "couldn't connect to host") Traceback (most recent call last): File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line 32, in __init__ self.curl.perform() error: (7, "couldn't connect to host")
Does Gwibber respect the Gnome Proxy Settings and use standard Web Ports? I'm behind an Squid Proxy with Authentication.
I'm getting a similar experience:
gwibber-service python2. 6/dist- packages/ gwibber/ microblog/ network. py", line 32, in __init__ curl.perform( ) python2. 6/dist- packages/ gwibber/ microblog/ network. py", line 32, in __init__ curl.perform( ) python2. 6/dist- packages/ gwibber/ microblog/ network. py", line 32, in __init__ curl.perform( )
Updating...
Traceback (most recent call last):
File "/usr/lib/
self.
error: (7, "couldn't connect to host")
Traceback (most recent call last):
File "/usr/lib/
self.
error: (7, "couldn't connect to host")
Traceback (most recent call last):
File "/usr/lib/
self.
error: (7, "couldn't connect to host")
Does Gwibber respect the Gnome Proxy Settings and use standard Web Ports? I'm behind an Squid Proxy with Authentication.