I get this bug using an Intel GPU but in one case only: when a program that is the drm master is running before I start the lightdm/unity system compositor (eg: xserver, another instance of mir, maybe plymouth...). A first idea is that we shouldn't call the drmSetInterfaceVersion before mir becomes the drm master - as we do atm. I will investigate though... :)
I get this bug using an Intel GPU but in one case only: when a program that is the drm master is running before I start the lightdm/unity system compositor (eg: xserver, another instance of mir, maybe plymouth...). A first idea is that we shouldn't call the drmSetInterface Version before mir becomes the drm master - as we do atm. I will investigate though... :)