Unfortunately no feedback from the libVNC crowd. But there had been a Mesa update (19.0.5), so I checked again, but the issue is still present. Will try again once 19.1 is out.