Gwibber not pulling feeds from all accounts

Bug #521569 reported by Simon Ives
154
This bug affects 30 people
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.)

Revision history for this message
Arnab Das (arnab-das) wrote :

+1 same problem here

Revision history for this message
Simon Ives (simon-simonives) wrote :

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)

Revision history for this message
Simon Ives (simon-simonives) wrote :

I'm not sure if this will be helpful but I get the following error whilst executing Gwibber from the command line:

simon@simon-laptop:~$ gwibber
No dbus monitor yet
Updating...
Updating...
ERROR:dbus.proxies:Introspect error on com.Gwibber.Accounts:/com/gwibber/Accounts: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Accounts was not provided by any .service files
ERROR:dbus.proxies:Introspect error on com.Gwibber.Streams:/com/gwibber/Streams: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Streams was not provided by any .service files
Updating...

Revision history for this message
Simon Ives (simon-simonives) wrote :

Just installed the current daily from the PPA (gwibber_2.29.1~bzr592-0ubuntu2~daily1~karmic) and the bug still remains.

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
Revision history for this message
Ryan Paul (segphault) wrote :

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?

Revision history for this message
Simon Ives (simon-simonives) wrote :
Download full text (5.4 KiB)

This is the screen dump from running gwibber-service from the command line:

simon@simon-laptop:~$ gwibber-service
DEBUG:root:Running Gwibber from the system path
Updating...
DEBUG:root:** Starting Refresh **
DEBUG:root:<flickr:images> Performing operation
DEBUG:root:<twitter:responses> Performing operation
DEBUG:root:<flickr:images> Operation failed
DEBUG:root:Traceback:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 47, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/flickr.py", line 81, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/flickr.py", line 85, in images
    user_id=self._getNSID(), format="json", nojsoncallback="1",
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/flickr.py", line 78, in _getNSID
    username=self.account["username"])["user"]["nsid"]
KeyError: 'user'

DEBUG:root:<twitter:receive> Performing operation
DEBUG:root:<twitter:responses> Finished operation
DEBUG:root:<twitter:private> Performing operation
DEBUG:root:<twitter:private> Finished operation
DEBUG:root:<facebook:receive> Performing operation
DEBUG:root:<twitter:receive> Operation failed
DEBUG:root:Traceback:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 47, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 131, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 134, in receive
    return self._get("statuses/home_timeline.json", count=count, since_id=since)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 119, in _get
    self.account["username"], self.account["password"]).get_json()
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line 28, in __init__
    self.curl.perform()
error: (28, 'Operation timed out after 15000 milliseconds with 79117 out of 268589 bytes received')

DEBUG:root:<identica:receive> Performing operation
DEBUG:root:<facebook:receive> Operation failed
DEBUG:root:Traceback:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 47, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 173, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 184, in receive
    data = self._get("stream.get", viewer_id=self.user_id, limit=80)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 60, in _get
    data = network.Download(URL_PREFIX, args, post).get_json()
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line 28, in __init__
    self.curl.perform()
error: (28, 'Oper...

Read more...

Revision history for this message
Simon Ives (simon-simonives) wrote :

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_activate() takes exactly 3 arguments (2 given)

Is this the expected behaviour or should I file another bug report?

Revision history for this message
Simon Ives (simon-simonives) wrote :

Starting Gwibber from the command line works, however, while gwibber-service is running. I'll submit a new bug report for this behaviour.

Revision history for this message
Simon Ives (simon-simonives) wrote :

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.

Revision history for this message
Simon Ives (simon-simonives) wrote :

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.

Revision history for this message
Simon Ives (simon-simonives) wrote :
Download full text (4.0 KiB)

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-laptop:~$ gwibber-service
DEBUG:root:Running Gwibber from the system path
Updating...
DEBUG:root:** Starting Refresh **
DEBUG:root:<facebook:receive> Performing operation
DEBUG:root:<facebook:images> Performing operation
DEBUG:root:<facebook:images> Operation failed
DEBUG:root:Traceback:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 49, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 191, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 223, in images
    """ % (self.user_id, limit))
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 63, in _get
    data = network.Download(URL_PREFIX, args, post).get_json()
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line 28, in __init__
    self.curl.perform()
error: (28, 'Operation timed out after 15000 milliseconds with 0 bytes received')

DEBUG:root:<facebook:receive> Operation failed
DEBUG:root:Traceback:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 49, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 191, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 202, in receive
    data = self._get("stream.get", viewer_id=self.user_id, limit=80)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 63, in _get
    data = network.Download(URL_PREFIX, args, post).get_json()
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line 28, in __init__
    self.curl.perform()
error: (28, 'Operation timed out after 15000 milliseconds with 0 bytes received')

DEBUG:root:<twitter:receive> Performing operation
DEBUG:root:<facebook:responses> Performing operation
DEBUG:root:<twitter:receive> Finished operation
DEBUG:root:<twitter:responses> Performing operation
DEBUG:root:<twitter:responses> Finished operation
DEBUG:root:<twitter:private> Performing operation
DEBUG:root:<twitter:private> Finished operation
DEBUG:root:<identica:receive> Performing operation
DEBUG:root:<facebook:responses> Finished operation
DEBUG:root:<identica:private> Performing operation
DEBUG:root:<identica:receive> Finished operation
DEBUG:root:<identica:responses> Performing operation
DEBUG:root:<identica:private> Finished operation
DEBUG:root:<flickr:images> Performing operation
DEBUG:root:<flickr:images> Operation failed
DEBUG:root:Traceback:
T...

Read more...

Revision history for this message
Simon Ives (simon-simonives) wrote :

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]).

Revision history for this message
Sense Egbert Hofstede (sense) wrote :

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.Accounts:/com/gwibber/Accounts: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Accounts was not provided by any .service files
2010-02-18 18:07:01,912 - Introspect error on com.Gwibber.Streams:/com/gwibber/Streams: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Streams was not provided by any .service files

Twitter seems to be the only not to work.

Revision history for this message
Sense Egbert Hofstede (sense) wrote :

The contents of the /usr/share/dbus-1/services/com.Gwibber.Service.service are:

[D-BUS Service]
Name=com.Gwibber.Service
Exec=/usr/bin/gwibber-service

The contents of the /usr/share/dbus-1/services/com.GwibberClient.service are:

[D-BUS Service]
Name=com.GwibberClient
Exec=/usr/bin/gwibber

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
Revision history for this message
Ken VanDine (ken-vandine) wrote :

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.

Revision history for this message
Simon Ives (simon-simonives) wrote :

Ken, new bug listed fot the timeout -> https://bugs.launchpad.net/gwibber/+bug/524132 <-

Lorenzo De Liso (blackz)
Changed in gwibber (Ubuntu):
status: New → Confirmed
Revision history for this message
Jacob Henderson (lmeditato) wrote :
Download full text (3.9 KiB)

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:responses> Performing operation
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/python2.6/dist-packages/gwibber/microblog/network.py", line 32, in __init__
    self.curl.perform()
error: (28, 'connect() timed out!')
Gwibber Dispatcher: ERROR Failed to communicate with https://api.facebook.com/restserver.php?api_key=71b85c6d8cb5bbb9f1a3f8bbdcdd4b05&v=1.0&sig=a369b56053fbd73c0059499e481dd3e2&format=json&query=%0A++++++SELECT+owner%2C+object_id%2C+created%2C+src_small%2C+src_big%2C+link%2C+caption%0A++++++++FROM+photo+WHERE+aid+in%0A++++++++%28SELECT+aid+FROM+album+WHERE+owner+IN%0A++++++++%28SELECT+uid2+FROM+friend+WHERE+uid1%3D1164601033%29%29%0A++++++++ORDER+BY+created+DESC+LIMIT+1%2C100%0A++++++&session_key=32ba28e8d9c78b4780cf32dd-1164601033&method=facebook.fql.query&call_id=1269548927000
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/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 64, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 198, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 233, in images
    return [self._image(post, profiles) for post in data]
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 165, in _image
    user = profiles[data["owner"]]
TypeError: string indices must be integers, not str

Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line 32, in __init__
    self.curl.perform()
error: (28, 'Operation timed out after 15000 milliseconds with 0 bytes received')
Gwibber Dispatcher: ERROR Failed to communicate with https://api.facebook.com/restserver.php?api_key=71b85c6d8cb5bbb9f1a3f8bbdcdd4b05&v=1.0&sig=ec8145df4edecf2669d5561d925ea735&format=json&query=%0A++++++SELECT+id%2C+post_id%2C+time%2C+fromid%2C+text%2C+object_id+FROM+comment+WHERE+post_id+IN%0A++++++++%28SELECT+post_id+FROM+stream+WHERE+source_id+%3D+1164601033%29+AND%0A++++++++fromid+%3C%3E+1164601033+ORDER+BY+time+DESC+LIMIT+1%2C100%0A++++++&session_key=32ba28e8d9c78b4780cf32dd-1164601033&method=facebook.fql.query&call_id=1269548921000
Gwibber Dispatcher: ERROR Failed to parse the response, error was: No JSON object could be decoded
Gwibber Dispatcher: ERROR <facebook:responses> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call las...

Read more...

Revision history for this message
mehul (mehul-forums) wrote :

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/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 75, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 146, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 149, in receive
    return self._get("statuses/home_timeline.json", count=count, since_id=since)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 136, in _get
    if data.has_key("error"):
AttributeError: 'list' object has no attribute 'has_key'

Revision history for this message
Joseph Fenell (josephfennellster) wrote :

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/python2.6/dist-packages/gwibber/microblog/network.py", line 32, in __init__
    self.curl.perform()
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 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
Updating...
Updating...
/usr/bin/gwibber:68: GtkWarning: gtk_container_add: assertion `GTK_IS_CONTAINER (container)' failed
  gtk.main()

** (gwibber:6604): CRITICAL **: murrine_style_draw_box: assertion `width >= -1' failed

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.

Revision history for this message
David Harper (inquisitivedave) wrote :

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.

Revision history for this message
Petter Sundlöf (petter-sundlof) wrote :

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 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
No dbus monitor yet
Updating...
Updating...
ERROR:dbus.proxies:Introspect error on com.Gwibber.Accounts:/com/gwibber/Accounts: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Accounts was not provided by any .service files
ERROR:dbus.proxies:Introspect error on com.Gwibber.Streams:/com/gwibber/Streams: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Streams was not provided by any .service files

Omer Akram (om26er)
Changed in gwibber (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Paul Jakma (paul+launchpad-jakma) wrote :

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).

Revision history for this message
Omer Akram (om26er) wrote :

@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

Revision history for this message
Simon Ives (simon-simonives) wrote :

@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.

Revision history for this message
Julien Olivier (julo) wrote :

Log from Gwibber 2.30.0.1 using one Facebook account.

Revision history for this message
Omer Akram (om26er) wrote : Re: [Bug 521569] Re: Gwibber not pulling feeds from all accounts

@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://launchpadlibrarian.net/48607581/gwibber.log
>
> --
> Gwibber not pulling feeds from all accounts
> https://bugs.launchpad.net/bugs/521569
> 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.)
>
>
>

Revision history for this message
Julien Olivier (julo) wrote :

My password add letters and digits. I changed it to only letters, and attached the new log.

Revision history for this message
Julien Olivier (julo) wrote :

Sorry, I meant "my password HAD letters and digits", of course...

Revision history for this message
larryni (larryni) wrote :

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:responses> Performing operation
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:responses> Finished operation
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']

Revision history for this message
Omer Akram (om26er) wrote :

This bug report have so many different logs that I cannot even change the description so that people dont get tricked with the title

Revision history for this message
mehul (mehul-forums) wrote :

This solution worked for me https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/533017/comments/25
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(data["created_at"])

Revision history for this message
mehul (mehul-forums) wrote :

Here's the problem:

-----xxxxx-----
In [23]: locale.getlocale()
Out[23]: ('en_IN', 'ISO8859-1')

In [24]: util.parsetime(data[0]['created_at'])
---------------------------------------------------------------------------
Error Traceback (most recent call last)

/usr/lib/python2.6/dist-packages/gwibber/microblog/<ipython console> in <module>()

/usr/lib/python2.6/dist-packages/gwibber/microblog/util/__init__.pyc in parsetime(t)
     10 locale.setlocale(locale.LC_TIME, 'C')
     11 result = mx.DateTime.Parser.DateTimeFromString(t)
---> 12 locale.setlocale(locale.LC_TIME, loc)
     13 return result.ticks()
     14

/usr/lib/python2.6/locale.pyc in setlocale(category, locale)
    511 # convert to string

    512 locale = normalize(_build_localename(locale))
--> 513 return _setlocale(category, locale)
    514
    515 def resetlocale(category=LC_ALL):

Error: unsupported locale setting

-----xxxxx-----

And it works if locale is en_US.utf8

-----xxxxx-----

In [25]: locale.setlocale(locale.LC_ALL,'en_US.utf8')
Out[25]: 'en_US.utf8'

In [26]: util.parsetime(data[0]['created_at'])
Out[26]: 1276948509.0
-----xxxxx-----

Revision history for this message
Omer Akram (om26er) wrote :

this bug is fixed in gwibber 2.30.1 and gwibber 2.31.2

Changed in gwibber:
status: New → Fix Released
Revision history for this message
Omer Akram (om26er) wrote :

gwibber 2.30.1 is in lucid-proposed.

Changed in gwibber (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Omer Akram (om26er) wrote :

gwibber 2.30.1 is now in Lucid updates.

Changed in gwibber (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.