Activating KMS GL driver in Raspbian Stretch allows lazycast to think it's running fine when it isn't actually displaying content

[JpTiger]

I compiled and installed Lazycast successfully on a Raspberry Pi Zero W (first gen) on Raspbian Stretch and later installed another program that required the full KMS driver to function. After switching drivers, Lazycast will run and connect to sources as normal, but the only thing that's dispalyed is the "Unnamed Window" that opens up, black. Deactivating the driver in raspi-config and rebooting allows Lazycast to run normally again, but of course breaks anything relying on the KMS driver. Not a huge deal as you're unlikely to need both running at once, but still not super convenient.

Main reason I'm posting is, while it would be nice if this were fixed to work with that driver, mostly I imagine people experiencing this issue will want to know about the cause and workaround described here.

[barhun]

Take a peek at the issue #100. Since the applications h264.bin and player.bin fail to access Broadcom VideoCore APIs under KMS, you need to choose gstreamer or vlc instead as the player lazycast launches after a successful connection.