@simon is this still an issue for you with gwibber 2.30? if so please do and attach the logs here
$ sudo pkill gwibber $ gwibber-service -d -o
@simon is this still an issue for you with gwibber 2.30? if so please do and attach the logs here
$ sudo pkill gwibber
$ gwibber-service -d -o