@aj00200: are you still getting this same problem? Or perhaps you had upgraded gwibber and the gwibber-service hadn't restarted since the upgrade?
Your particular traceback looks like the gwibber-service process you had running was from 2.32 and the client was 3.0. If you are still getting this same error, please open a new bug for it.
@aj00200: are you still getting this same problem? Or perhaps you had upgraded gwibber and the gwibber-service hadn't restarted since the upgrade?
Your particular traceback looks like the gwibber-service process you had running was from 2.32 and the client was 3.0. If you are still getting this same error, please open a new bug for it.