I had similar problems to those above. It seemed at first to be a Facebook problem, as I had just added my Facebook account. However, it turned out it was actually a network issue and the gwibber-service was failing to update both Facebook and Twitter streams. You can see this is happening in the logs quoted above as well:
error: (28, 'connect() timed out!') In my case, I got things working by editing /etc/resolv.conf and adding the Google and Level 3 nameservers, in addition to the crappy wifi router I am using: $ cat /etc/resolv.conf # Generated by NetworkManager nameserver 8.8.8.8 nameserver 4.2.2.2 nameserver 192.168.1.1 My theory: The timeouts for connecting and receiving data may simply be too short for many folks out there. Using a faster nameserver worked for me, at least temporarily. But it is just a workaround, the gwibber service should probably be a little more tolerant of poor networks. Hope this helps someone. -- Gwibber not retrieving Facebook info https://bugs.launchpad.net/bugs/549755 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
