The most recent update to the Testing channel should now include the related change: V5.0+ Testing Channel Changelog - #4 by phillxnet
It should hopefully fix your issue, or at least help us narrow it down.
As mentioned in that post, a reboot may be required.