Gwibber Not Updating..

[varun kumar]

Binary package hint: gwibber

Gwibber Not updating..Tried several times..Issue facing since i installed ubuntu 11.04 Natty...Some times twitter updates,some times it doesn't...Facebook,not updating from the first time..
---
Architecture: i386
DistroRelease: Ubuntu 11.04
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
Package: gwibber 3.0.0.1-0ubuntu2
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, user)
 LANG=en_IN.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Tags: natty
Uname: Linux 2.6.38-8-generic i686
UpgradeStatus: Upgraded to natty on 2011-04-13 (16 days ago)
UserGroups: adm admin audio cdrom dialout dip disk fax floppy fuse lpadmin netdev plugdev sambashare tape tty vboxusers video voice

[Joshua Lückers (joshualuckers)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 762783
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[varun kumar (varunkumar-eie)]

apport information

[A Wolf (amin--14)]

same prob here

[Victor Vargas (kamus)]

varun, Please could you attach your "~/.cache/gwibber/gwibber.log" as a separated file? Thank you

[varun kumar (varunkumar-eie)]

Hello,

Please find the compressed file
On 5/1/11, Kamus <email address hidden> wrote:
> varun, Please could you attach your "~/.cache/gwibber/gwibber.log" as a
> separated file? Thank you
>
> ** Changed in: gwibber (Ubuntu)
> Importance: Undecided => Medium
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/762783
>
> Title:
> Gwibber Not Updating..
>
> Status in “gwibber” package in Ubuntu:
> New
>
> Bug description:
> Binary package hint: gwibber
>
> Gwibber Not updating..Tried several times..Issue facing since i installed
> ubuntu 11.04 Natty...Some times twitter updates,some times it
> doesn't...Facebook,not updating from the first time..
> ---
> Architecture: i386
> DistroRelease: Ubuntu 11.04
> InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
> Package: gwibber 3.0.0.1-0ubuntu2
> PackageArchitecture: all
> ProcEnviron:
> LANGUAGE=en_IN:en
> PATH=(custom, user)
> LANG=en_IN.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
> Tags: natty
> Uname: Linux 2.6.38-8-generic i686
> UpgradeStatus: Upgraded to natty on 2011-04-13 (16 days ago)
> UserGroups: adm admin audio cdrom dialout dip disk fax floppy fuse lpadmin
> netdev plugdev sambashare tape tty vboxusers video voice
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/762783/+subscribe
>

[Swâmi Petaramesh (swami-petaramesh)]

Affecting me as well on Natty. Gwibber set to update twitter account every 5 minutes... Upgrades it, then nothing for 24 hours (!), then one update, then nothing for 4 hours (!).

Additionally there's no way to know if "F5 update" does anything at all except by seing that no new messages appear... Gwibber is so unconsistent that I consider reverting to KDE just because Choqok works so much better than Gwibber does... And I badly need a reliable Twitter.

[Swâmi Petaramesh (swami-petaramesh)]

Adding the end of my .cache/gwibber/gwibber.log :

Looks like massive network "timeouts". Allright my Internet connection is SLOW and VERY SLOW, but well it works perfectly besides being slow. (And worked perfectly in KDE/Choqok)

2011-05-01 22:23:43,050 - Twitter - INFO - Dispatcher Online, initiating a refresh
2011-05-01 22:23:43,051 - Gwibber GNOME Client - INFO - Setting to Online
2011-05-01 22:24:05,504 - Twitter - ERROR - Network failure - error: 28 - SSL connection timeout at 138885
2011-05-01 22:24:05,505 - Twitter - ERROR - <twitter:responses> Operation failed
2011-05-01 22:24:10,299 - Twitter - ERROR - Network failure - error: 28 - SSL connection timeout at 134094
2011-05-01 22:24:10,300 - Twitter - ERROR - <twitter:receive> Operation failed
2011-05-01 22:24:16,415 - Twitter - ERROR - Network failure - error: 28 - SSL connection timeout at 140099
2011-05-01 22:24:16,416 - Twitter - ERROR - <twitter:private> Operation failed
2011-05-01 22:24:16,418 - Twitter - INFO - Loading complete: 56 - []
2011-05-01 22:25:41,867 - Twitter - ERROR - Network failure - error: 28 - SSL connection timeout at 139698
2011-05-01 22:25:41,867 - Twitter - ERROR - <twitter:receive> Operation failed
2011-05-01 22:25:47,483 - Twitter - ERROR - Network failure - error: 28 - SSL connection timeout at 134082
2011-05-01 22:25:47,483 - Twitter - ERROR - <twitter:responses> Operation failed
2011-05-01 22:25:51,154 - Twitter - ERROR - Network failure - error: 28 - SSL connection timeout at 141726
2011-05-01 22:25:51,154 - Twitter - ERROR - <twitter:private> Operation failed
2011-05-01 22:25:51,156 - Twitter - INFO - Loading complete: 57 - []
2011-05-01 22:30:38,984 - Twitter - ERROR - Network failure - error: 28 - SSL connection timeout at 142394
2011-05-01 22:30:38,985 - Twitter - ERROR - <twitter:receive> Operation failed
2011-05-01 22:30:44,517 - Twitter - ERROR - Network failure - error: 28 - SSL connection timeout at 136853
2011-05-01 22:30:44,518 - Twitter - ERROR - <twitter:responses> Operation failed
2011-05-01 22:30:47,708 - Twitter - ERROR - Network failure - error: 28 - SSL connection timeout at 142290
2011-05-01 22:30:47,709 - Twitter - ERROR - <twitter:private> Operation failed
2011-05-01 22:30:47,711 - Twitter - INFO - Loading complete: 58 - []

[Ethan Glasser-Camp (ethan-glasser-camp)]

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

[Ethan Glasser-Camp (ethan-glasser-camp)]

Hi,

I dug in a little deeper, rebuilt the libcurl3-gnutls package, and found what I believe to be the culprit:

https://github.com/bagder/curl/commit/cbf4961bf3e42d88f6489f981efd509faa86f501#L0L219

In previous editions of libcurl-gnutls, the line of gtls.c in question reads:

      what = Curl_socket_ready(readfd, writefd,
                               nonblocking?0:(int)timeout_ms);

Now, it reads:

      what = Curl_socket_ready(readfd, writefd,
                               nonblocking?0:(int)timeout_ms);

The effect is that where previously, the the SSL handshake would block "as long as it took" to complete the handshake. Now, it only waits for one second. If your connection is fast enough, it works fine. But if you're on a crappy high-latency CDMA modem on a state-run telecom in Africa, you get "SSL timeouts".

The commit also links to this bug report:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594150

It seems like this change was made because SSL connection timeouts were covering other bugs. Note also that if you rebuild the curl package, you can witness this failure "by hand".

ethan@jonah-hex:~/software/curl-7.21.3$ ./debian/build-gnutls/src/curl https://github.com
curl: (28) SSL connection timeout at 297679

I'm not completely sure about what the fix is here. I am going to report the bug upstream and see what happens.

Ethan

[Ethan Glasser-Camp (ethan-glasser-camp)]

I emailed upstream: http://curl.haxx.se/mail/lib-2011-05/0167.html

They committed a fix:

https://github.com/bagder/curl/commit/d4e000906ac4ef243258a5c9a819a7cde247d16a

As you can see, the patch is pretty simple. Can we put this in libcurl and rebuild?

Ethan