To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.
Depending on the used skin you have to set the settings-level to standard or higher, in summary:
enable debug logging at settings->system->logging
reboot the OSMC device twice(!)
reproduce the issue
upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A
publish the provided URL from the log set upload, here
Thanks for your understanding. We hope that we can help you get up and running again shortly.
(or that’s what the Log Uploader screen shows - I have no idea whether that’s what I’m supposed to provide, or if I’m supposed to do something else now… the instructions are a little confusing for me, and that URL gives me a whole lot of nothing when I try to access it!).
I’d pretty much got there just after you’d posted (I’ve been annoying my wife and kids, playing around with the TV and Vero constantly all morning) but it gave me the confidence that I was now working along the right lines, as I’d mis-used the whitelist (thinking the highlighting worked in reverse!).
All now working perfectly in time for the wife to watch her nation’s rugby team (and hog the TV).