2017-01-15, 18:41
JethroCl - I have the exact same setup and behavior with this screensaver. I think it is because our "parents" profile is the renamed "masterprofile". That's the only way I can explain why the "master lock" is tethered to the "parents" profile lock code.
I think I may have found a workaround: In the profile settings area, disable the login screen and have Kodi automatically log in to your "kids" profile. On my system (16.1 running on Retropie), the login screen no longer prompts for the "master lock" when the screensaver triggers a logout.
Of course, this only works well if you seldom restart Kodi. Otherwise you'll need to log out of your "kids" profile and into your own every time you start up. Since I'm running on a pi, I almost never reboot so it doesn't matter that my system logs into my "kids" profile on first boot.
Hope this works for you!
I think I may have found a workaround: In the profile settings area, disable the login screen and have Kodi automatically log in to your "kids" profile. On my system (16.1 running on Retropie), the login screen no longer prompts for the "master lock" when the screensaver triggers a logout.
Of course, this only works well if you seldom restart Kodi. Otherwise you'll need to log out of your "kids" profile and into your own every time you start up. Since I'm running on a pi, I almost never reboot so it doesn't matter that my system logs into my "kids" profile on first boot.
Hope this works for you!
