Comment 5 for bug 521569

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?