Tadeás, please could you check if this behaviour is still occurring with latest release of gwibber 3.0.0.1?
Tadeás, please could you check if this behaviour is still occurring with latest release of gwibber 3.0.0.1?