Gwibber not pulling feeds from all accounts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gwibber |
Fix Released
|
Undecided
|
Unassigned | ||
gwibber (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
On 13 February 2010 my Gwibber daily install (2.29.1) has stopped pulling tweets etc. from my Twitter account and has stopped pulling updates from my Facebook account. Gwibber's functionality in pulling dents from Identi.ca is still working flawlessly.
Posting updates to all three accounts is working fine and the updates that I'm posting to Twitter are displaying in Gwibber (just no other tweets, @replies etc.)

Arnab Das (arnab-das) wrote : | #1 |

Simon Ives (simon-simonives) wrote : | #2 |
I've reinstalled the daily from today in case there was an issue with the earlier update, but the problem still remains and it's a little worse than my earlier report.
I have four accounts within Gwibber: Twitter, Identi.ca, Facebook, and Flickr.
Any posts I forward to Twitter, Identi.ca and Facebook are uploaded to each service without issue. Any posts I forward to Twitter and Identi.ca are displayed in the appropriate area within Gwibber. Any posts I forward to Facebook are not displayed within Gwibber.
Gwibber is not displaying anything at all from Facebook and Flickr, and it's only displaying my own posts from Twitter and Identi.ca.
Could this be a timeout issue?
(Gwibber 2.29.1 Daily on Ubuntu 9.10)

Simon Ives (simon-simonives) wrote : | #3 |
I'm not sure if this will be helpful but I get the following error whilst executing Gwibber from the command line:
simon@simon-
No dbus monitor yet
Updating...
Updating...
ERROR:dbus.
ERROR:dbus.
Updating...

Simon Ives (simon-simonives) wrote : | #4 |
Just installed the current daily from the PPA (gwibber_
Some updates:
The current daily included the new options for Facebook including messages, images, and sent items. Interestingly, Gwibber is still not pulling information from all accounts except my own updates to Twitter and Identi.ca - but it is pulling images from Facebook. It's not pulling Facebook messages or sent items, but it is pulling images.
I'm still getting the same dbus error mentioned in my previous post.
Changed in gwibber: | |
milestone: | none → 2.30.0 |

Ryan Paul (segphault) wrote : | #5 |
I'm not sure what could be causing this, but it might be helpful if I could see backend error messages. Could you kill both gwibber and gwibber-service and then try manually running gwibber-service from the command line?

Simon Ives (simon-simonives) wrote : | #6 |
This is the screen dump from running gwibber-service from the command line:
simon@simon-
DEBUG:root:Running Gwibber from the system path
Updating...
DEBUG:root:** Starting Refresh **
DEBUG:root:
DEBUG:root:
DEBUG:root:
DEBUG:root:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
user_
File "/usr/lib/
username=
KeyError: 'user'
DEBUG:root:
DEBUG:root:
DEBUG:root:
DEBUG:root:
DEBUG:root:
DEBUG:root:
DEBUG:root:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return self._get(
File "/usr/lib/
self.
File "/usr/lib/
self.
error: (28, 'Operation timed out after 15000 milliseconds with 79117 out of 268589 bytes received')
DEBUG:root:
DEBUG:root:
DEBUG:root:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
data = self._get(
File "/usr/lib/
data = network.
File "/usr/lib/
self.
error: (28, 'Oper...

Simon Ives (simon-simonives) wrote : | #7 |
Further, while gwibber-service is running from the command line I am unable to start Gwibber from the taskbar indicator (clicking the Ubuntu taskbar "mail icon" and selecting "Gwibber"). The error on the command line given for this is:
TypeError: on_indicator_
Is this the expected behaviour or should I file another bug report?

Simon Ives (simon-simonives) wrote : | #8 |
Starting Gwibber from the command line works, however, while gwibber-service is running. I'll submit a new bug report for this behaviour.

Simon Ives (simon-simonives) wrote : | #9 |
It seems that gwibber-service is timing out before it can receive all of the data. Perhaps 1.5 seconds isn't long enough for Gwibber users with limited bandwidth?
Anyhow, I'll take my computer to work tomorrow and try it out on the faster network to see if this fixes the issues.

Simon Ives (simon-simonives) wrote : | #10 |
- Screen dump from running gwibber-service on the command line Edit (5.4 KiB, text/plain)
I've attached the above screen dump as a text file. I get a different result in each section, and on the last line, every time I run gwibber-service though. I still get the same results in the Gwibber client though.

Simon Ives (simon-simonives) wrote : | #11 |
I've just started gwibber-service at work and I'm getting better results (see below).
Should I lodge a separate bug stating that Gwibber only works on high bandwidth Internet connections or am I misreading the output? (My workplace, due to our location - Mount Isa Queensland Australia - has limited bandwidth, but better than what I get at home)
simon@simon-
DEBUG:root:Running Gwibber from the system path
Updating...
DEBUG:root:** Starting Refresh **
DEBUG:root:
DEBUG:root:
DEBUG:root:
DEBUG:root:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
""" % (self.user_id, limit))
File "/usr/lib/
data = network.
File "/usr/lib/
self.
error: (28, 'Operation timed out after 15000 milliseconds with 0 bytes received')
DEBUG:root:
DEBUG:root:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
data = self._get(
File "/usr/lib/
data = network.
File "/usr/lib/
self.
error: (28, 'Operation timed out after 15000 milliseconds with 0 bytes received')
DEBUG:root:
DEBUG:root:
DEBUG:root:
DEBUG:root:
DEBUG:root:
DEBUG:root:
DEBUG:root:
DEBUG:root:
DEBUG:root:
DEBUG:root:
DEBUG:root:
DEBUG:root:
DEBUG:root:
DEBUG:root:
DEBUG:root:
DEBUG:root:
T...

Simon Ives (simon-simonives) wrote : | #12 |
- low-bandwidth_gwibber-service.txt Edit (5.4 KiB, text/plain)
I've attached the gwibber-service terminal output as a text file to this response for easier comparison between the two (one at home on limited bandwidth [64k] and one at work on medium bandwidth [1200k]).

Sense Egbert Hofstede (sense) wrote : | #13 |
I can confirm this bug on Ubuntu 10.04 with Gwibber 2.29.90-0ubuntu1.
2010-02-18 18:07:01,911 - Introspect error on com.Gwibber.
2010-02-18 18:07:01,912 - Introspect error on com.Gwibber.
Twitter seems to be the only not to work.

Sense Egbert Hofstede (sense) wrote : | #14 |
The contents of the /usr/share/
[D-BUS Service]
Name=com.
Exec=/usr/
The contents of the /usr/share/
[D-BUS Service]
Name=com.
Exec=/usr/
This are all Gwibber .service files, it seems that the Gwibber client is trying to use some DBus interfaces that don't exist.
Changed in gwibber (Ubuntu): | |
milestone: | none → ubuntu-10.04-beta-1 |

Ken VanDine (ken-vandine) wrote : | #15 |
The dbus .service files stuff is really just noise, we need to fix it but that isn't related to your bug. When the client starts it spams the service and fails to introspect all the dbus names it expects, I haven't tracked down why. I haven't seen any evidence that it breaks anything.
The network timeout that was commented on should be filed as a separate bug.

Simon Ives (simon-simonives) wrote : | #16 |
Ken, new bug listed fot the timeout -> https:/
Changed in gwibber (Ubuntu): | |
status: | New → Confirmed |

Jacob Henderson (lmeditato) wrote : | #17 |
Here is my debug mode error code:
Updating...
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Monitors are up
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG ** Starting Refresh - Thu Mar 25 16:28:41 2010 **
Gwibber Dispatcher: DEBUG <facebook:
Gwibber Dispatcher: DEBUG <facebook:receive> Performing operation
Gwibber Dispatcher: DEBUG <facebook:receive> Finished operation
Gwibber Dispatcher: DEBUG <facebook:images> Performing operation
Traceback (most recent call last):
File "/usr/lib/
self.
error: (28, 'connect() timed out!')
Gwibber Dispatcher: ERROR Failed to communicate with https:/
Gwibber Dispatcher: ERROR Failed to parse the response, error was: No JSON object could be decoded
Gwibber Dispatcher: ERROR <facebook:images> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return [self._image(post, profiles) for post in data]
File "/usr/lib/
user = profiles[
TypeError: string indices must be integers, not str
Traceback (most recent call last):
File "/usr/lib/
self.
error: (28, 'Operation timed out after 15000 milliseconds with 0 bytes received')
Gwibber Dispatcher: ERROR Failed to communicate with https:/
Gwibber Dispatcher: ERROR Failed to parse the response, error was: No JSON object could be decoded
Gwibber Dispatcher: ERROR <facebook:
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call las...

mehul (mehul-forums) wrote : | #18 |
I am facing the same error too with twitter but facebook works for me.
Here's the error log
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: ERROR <twitter:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return self._get(
File "/usr/lib/
if data.has_
AttributeError: 'list' object has no attribute 'has_key'

Joseph Fenell (josephfennellster) wrote : | #19 |
I'm facing this error as well, here's what I get when running 'gwibber-service' and gwibber from command-line respectively
Traceback (most recent call last):
File "/usr/lib/
self.
error: (6, 'name lookup timed out')
and
** (gwibber:6604): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:6604): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:6604): WARNING **: Trying to register gtype 'WnckWindowMove
Updating...
Updating...
/usr/bin/
gtk.main()
** (gwibber:6604): CRITICAL **: murrine_
I've went to network.py, which is dead in the middle of 'CurlDownloader:' from looking at everyone else's problems it begins with CurlDownloader. Sorry my programming skills are sub-par or I would see what I could do.

David Harper (inquisitivedave) wrote : | #20 |
I'm getting a similar experience:
gwibber-service
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.

Petter Sundlöf (petter-sundlof) wrote : | #21 |
Same issue. But NO feeds at all.
petter@gunilla:~$ gwibber
** (gwibber:5729): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:5729): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:5729): WARNING **: Trying to register gtype 'WnckWindowMove
No dbus monitor yet
Updating...
Updating...
ERROR:dbus.
ERROR:dbus.
Changed in gwibber (Ubuntu): | |
importance: | Undecided → Medium |

Paul Jakma (paul+launchpad-jakma) wrote : | #22 |
Bugs #530195 and #554999 may be very similar to this one. I also twitter not updating for hours/days at a time (even when replies/searches are working).

Omer Akram (om26er) wrote : | #23 |
@simon is this still an issue for you with gwibber 2.30? if so please do and attach the logs here
$ sudo pkill gwibber
$ gwibber-service -d -o

Simon Ives (simon-simonives) wrote : | #24 |
@Omar - I've only got my work computer (Win 7) for the next week or so and will get onto the logs when I get back home. I've only had similar issues with Gwibber 2.30 with *very* slow internet connections which, I assume, has more to do with the internet connection than anything else. Consequently, I doubt that my logs will show anything of consequence as I'm not going to have sat based internet access for a while.

Julien Olivier (julo) wrote : | #25 |

Omer Akram (om26er) wrote : Re: [Bug 521569] Re: Gwibber not pulling feeds from all accounts | #26 |
@julien, which type of password are you using mean are there any decimals
between the pasword? can you try to change it to some normal characters
On Mon, May 17, 2010 at 7:39 PM, Julien Olivier <email address hidden> wrote:
> Log from Gwibber 2.30.0.1 using one Facebook account.
>
> ** Attachment added: "gwibber.log"
> http://
>
> --
> Gwibber not pulling feeds from all accounts
> https:/
> You received this bug notification because you are subscribed to gwibber
> in ubuntu.
>
> Status in Gwibber: New
> Status in “gwibber” package in Ubuntu: Confirmed
>
> Bug description:
> On 13 February 2010 my Gwibber daily install (2.29.1) has stopped pulling
> tweets etc. from my Twitter account and has stopped pulling updates from my
> Facebook account. Gwibber's functionality in pulling dents from Identi.ca
> is still working flawlessly.
>
> Posting updates to all three accounts is working fine and the updates that
> I'm posting to Twitter are displaying in Gwibber (just no other tweets,
> @replies etc.)
>
>
>

Julien Olivier (julo) wrote : | #27 |
- gwibber.log Edit (3.3 KiB, text/plain)
My password add letters and digits. I changed it to only letters, and attached the new log.

Julien Olivier (julo) wrote : | #28 |
Sorry, I meant "my password HAD letters and digits", of course...

larryni (larryni) wrote : | #29 |
I'm having the same problem with my Twitter feed not loading since last night - Ubuntu 10.04, Gwibber 2.30.0.1.
Output from gwibber-service -d -o:
Updating...
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Monitors are up
Gwibber Dispatcher: INFO Gwibber Service is reloading account credentials
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG ** Starting Refresh - Fri May 21 13:34:19 2010 **
Gwibber Dispatcher: DEBUG <flickr:images> Performing operation
Gwibber Dispatcher: DEBUG <identica:
Gwibber Dispatcher: DEBUG <identica:receive> Performing operation
Gwibber Dispatcher: DEBUG <identica:private> Performing operation
Gwibber Dispatcher: DEBUG <flickr:images> Finished operation
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: DEBUG <identica:
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <identica:private> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: DEBUG <identica:receive> Adding record
Gwibber Dispatcher: DEBUG <identica:receive> Finished operation
Gwibber Dispatcher: DEBUG Checking message 33051082 timestamp (2010-05-21 13:33:06.00) to see if it is newer than 2010-05-21 13:24:20.65
Gwibber Dispatcher: DEBUG Message 33051082 newer than 2010-05-21 13:24:20.65, notifying
Gwibber Dispatcher: DEBUG <twitter:receive> Finished operation
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: INFO Loading complete: 1 - ['Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success']

Omer Akram (om26er) wrote : | #30 |
This bug report have so many different logs that I cannot even change the description so that people dont get tricked with the title

mehul (mehul-forums) wrote : | #31 |
This solution worked for me https:/
I set the locale to en_US.utf8 and then started the gwibber-service and things were working perfectly.
My locale earlier was en_IN and at that time gwibber was failing at the following line:
m["time"] = util.parsetime(

mehul (mehul-forums) wrote : | #32 |
Here's the problem:
-----xxxxx-----
In [23]: locale.getlocale()
Out[23]: ('en_IN', 'ISO8859-1')
In [24]: util.parsetime(
-------
Error Traceback (most recent call last)
/usr/lib/
/usr/lib/
10 locale.
11 result = mx.DateTime.
---> 12 locale.
13 return result.ticks()
14
/usr/lib/
511 # convert to string
512 locale = normalize(
--> 513 return _setlocale(
514
515 def resetlocale(
Error: unsupported locale setting
-----xxxxx-----
And it works if locale is en_US.utf8
-----xxxxx-----
In [25]: locale.
Out[25]: 'en_US.utf8'
In [26]: util.parsetime(
Out[26]: 1276948509.0
-----xxxxx-----

Omer Akram (om26er) wrote : | #33 |
this bug is fixed in gwibber 2.30.1 and gwibber 2.31.2
Changed in gwibber: | |
status: | New → Fix Released |

Omer Akram (om26er) wrote : | #34 |
gwibber 2.30.1 is in lucid-proposed.
Changed in gwibber (Ubuntu): | |
status: | Confirmed → Fix Committed |

Omer Akram (om26er) wrote : | #35 |
gwibber 2.30.1 is now in Lucid updates.
Changed in gwibber (Ubuntu): | |
status: | Fix Committed → Fix Released |
+1 same problem here