Gwibber fails on processing specific tweet

It's not limited to that account, it seems to be a parsing problem in general. Here's mine:

2011-02-02 14:46:18,186 - Gwibber Dispatcher - ERROR - Twitter failure - {u'favorited': False, u'contributors': None, u'truncated': False, u'text': u'Dear Lazy Twitter: How do I compare "&aacute;" and "\xe1" in Javascript to get True?', u'user': {u'follow_request_sent': False, u'profile_use_background_image': True, u'id': 5881942, u'verified': False, u'profile_sidebar_fill_color': u'efefef', u'profile_text_color': u'333333', u'followers_count': 286, u'protected': False, u'location': u'Porto Alegre, RS, Brazil', u'profile_background_color': u'131516', u'id_str': u'5881942', u'utc_offset': -10800, u'statuses_count': 11695, u'description': u'Old school coder living in a 2.0 development world.', u'friends_count': 232, u'profile_link_color': u'095d99', u'profile_image_url': u'http://a2.twimg.com/profile_images/1033692480/Screen_shot_2010-04-06_at_8.07.07_PM_normal.png', u'is_translator': False, u'show_all_inline_media': False, u'geo_enabled': False, u'profile_background_image_url': u'http://a2.twimg.com/a/1296156503/images/themes/theme15/bg.png', u'name': u'Julio Biason', u'lang': u'en', u'profile_background_tile': True, u'favourites_count': 8, u'screen_name': u'juliobiason', u'notifications': False, u'url': u'http://juliobiason.net', u'created_at': u'Wed May 09 01:15:26 +0000 2007', u'contributors_enabled': False, u'time_zone': u'Brasilia', u'profile_sidebar_border_color': u'eeeeee', u'following': True, u'listed_count': 11}, u'retweeted': False, u'in_reply_to_status_id_str': None, u'coordinates': None, u'id': 32416720706609154, u'source': u'<a href="http://itunes.apple.com/us/app/twitter/id409789998?mt=12" rel="nofollow">Twitter for Mac</a>', u'in_reply_to_status_id': None, u'in_reply_to_screen_name': None, u'in_reply_to_user_id': None, u'place': None, u'created_at': u'Tue Feb 01 12:35:23 +0000 2011', u'retweet_count': 0, u'geo': None, u'in_reply_to_user_id_str': None, u'id_str': u'32416720706609154'}

2011-02-02 14:46:18,267 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed

This might be a recent change in Twitter's feed, I've never had it happen before.

I'm on maverick:
gwibber 2.32.2-0ubuntu2
gwibber-service 2.32.2-0ubuntu2
libgwibber0 0.0.6-0ubuntu1

I'm getting errors that look like this

2011-02-14 12:49:27,774 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2011-02-14 12:49:27,779 - Gwibber Dispatcher - ERROR - Twitter unexpected result - No JSON object could be decoded

Hi Andrew,

do you experience the same symptoms as described in the description (Gwibber stopped fetching entries from twitter)? I am not sure if the error messages you posted are related to the same bug.

I have seen this issue before, but I can't remember for now the report number. any way, have you tried to unfollow 'urbanrivals' user and then check if this behaviour is still occurring?

Thanks for your reply. As I tried to explain in the description, unfollowing 'urbanrivals' did restore gwibbers normal behaviour. When I then tried to follow 'urbanrivals' again the same error occured and gwibber stopped fetching any tweets, but still showing all tweets fetched until then. So the issue was reproducible for me at that time.

In fact, now that gwibber does not try to fetch that tweet in question any more (because it is too old) I am able follow 'urbanrivals' with gwibber without a problem.

There are no open questions so I set the status back to new.

Jon, is there any possibility to check if this behaviour is still affecting you with gwibber 3.0.0.1? Thanks

Sorry, I have not noticed your answer until now.

I don’t know a way to reproduce this with any version of gwibber, due to the fact that gwibber fetches only the messages of the last few days/hours. If you can tell me how to configure gwibber to fetch tweets from a specific period of time instead of the most recent ones I will try it out. Otherwise this bug is hard to reproduce as I stated in the description because it’s connected to something in one specific tweet.

Perhaps there is a way to reproduce this tweet (http://twitter.com/#!/urbanrivals/status/30986263850913792) so that it recreates the error. But unfortunately I don’t have the time to look into the twitter API and test this out.

Folks, any news about this issue? are you still being affected by this behaviour?
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Thank you for taking the time to report this bug and helping to make Ubuntu better,
* can you reproduce it ?
* if so than which version are you on ?

The short answer: No. I cannot reproduce this bug.

The long answer: It is very hard to reproduce this bug. I do not know the exact criteria gwibber uses to fetch messages, but it does not fetch messages older than a certain number of days. Once the tweet, that probably caused this malfunction, was older than this threshold gwibber started working normally for me and I could not reproduce this bug with the same version of gwibber. There is no way for me to tell if any later version of gwibber would behave the same way when encountering the tweet in question. I have never encounterd the same malfunction again with another tweet.

The only way I can think of to reproduce this bug is to use a mock-up of the twitter api and recreate the tweet mentioned in the log file I posted. I do not have the knowledge to do this. I do not know if the twitter api has changed since then so this would be impossible. I do not know if the parts of the gwibber code that could be responsible have been rewritten by now so this would be irrelevant.

Conclusion: This bug seems to affect only very few people and occurs very rarely. When it occurs gwibber stops working completely for a number of days. It may be gone in a current version of gwibber and it is propably not worth the effort to investigate any further. If you want to close this ticket I have no objection.

[Expired for gwibber (Ubuntu) because there has been no activity for 60 days.]