This issue has no longer been visible for a while; we can't but assume at the moment that the move to GNOME 3.36 might have had something to do with it.