The same problem appeared again a few days ago after the qgnomeplatform updates. So, it looks like every time this is updated the problem comes back.