Hello again, @Jorma_Tuomainen 
I was just about to write that @phillxnet worked hard to get the next release in the Testing channel out, which includes a fix for this issue: V5.0+ Testing Channel Changelog - #4 by phillxnet. As mentioned in that post, note that a reboot may be required here.