Comment 2 for bug 523964

I am able to work around this by killing and restarting gwibber and gwibber-service, but I haven't figured out what causes it in the first place. The other gwibber problem I have at the moment is bug 522067, but I have no reason to believe it's related yet.