Comment 12 for bug 709865

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.