This turns out to have been a bug in an Intel graphics driver. Can be fixed properly by updating to a new version of the driver:
Many thanks @Andrea_Adriano for the intervening workaround!
This turns out to have been a bug in an Intel graphics driver. Can be fixed properly by updating to a new version of the driver:
Many thanks @Andrea_Adriano for the intervening workaround!