Thanks for the information! We got access to an old machine with an Intel HD 4000, and can confirm the issue. At the moment though, because these chips are so old and no longer supported by the manufacturer, we do not plan on patching for this right now. We can try and investigate installing a workaround for this driver bug in 4.30, especially if more people start running into this.