Hi, I'm suffering from a similar bug with a similar error message in the
log.  To try to debug it, I added the following line to
/usr/lib/python2.7/dist-packages/gwibber/microblog/network.py:

    self.curl.setopt(pycurl.VERBOSE, 1)

With this, gwibber-service -o -d tells me:

Loading plugin Twitter version 1.0
Twitter     : DEBUG    Setting up monitors
Twitter     : DEBUG    Refresh interval is set to 15
Twitter     : DEBUG    ** Starting Refresh - 2011-05-17 16:49:02.83 **
Twitter     : DEBUG    <twitter:responses> Performing operation
Twitter     : DEBUG    <twitter:receive> Performing operation
* About to connect() to api.twitter.com port 443 (#0)
*   Trying 199.59.149.200... * About to connect() to api.twitter.com port 443 
(#0)
*   Trying 199.59.148.20... * connected
* Connected to api.twitter.com (199.59.149.200) port 443 (#0)
* found 142 certificates in /etc/ssl/certs/ca-certificates.crt
* connected
* Connected to api.twitter.com (199.59.148.20) port 443 (#0)
* found 142 certificates in /etc/ssl/certs/ca-certificates.crt
* SSL connection timeout at 146598
* Closing connection #0
Twitter     : ERROR    Network failure - error: 28 - SSL connection timeout at 
146598
Twitter     : DEBUG    Failed to parse the response, error was: No JSON object 
could be decoded
Twitter     : ERROR    <twitter:responses> Operation failed

(With a similar message for my identi.ca account.)

I dug a little more and found this thread:

http://curl.haxx.se/mail/lib-2011-05/0015.html

It looks like connecting with OpenSSL works, but pycurl is built to use
curl with GnuTLS instead, and for some reason it's causing a timeout.  I
should note that the "timeout" I'm experiencing is very quick -- 6 or 7
seconds.

I'm using the version of gwibber in the gwibber-daily ppa.  libgnutls26
is version 2.8.6-1ubuntu2.

Hopefully this helps someone else track this down!

Ethan

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/762783

Title:
  Gwibber Not Updating..

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to