Lowering the setting and unassigning, so what happens, happened there is that guest-account calls:
" gconftool-2 --set --type bool /desktop/gnome/lockdown/disable_lock_screen True"
or gnome-screensaver migrated to gsettings...
it happens to work because the gconf keys are migrated to gsettings on login, the migration binary was buggy in gconf 2.32.4 (which exposed this bug) and is fixed again in 2.32.5
we should change that for a gsettings,dconf use but desrt recommended to way for dconf changes he added to his todolist to be able to create a db without needing to spawn a session bus, the current works until we do it this way, which should be before the lts
Lowering the setting and unassigning, so what happens, happened there is that guest-account calls: gnome/lockdown/ disable_ lock_screen True"
" gconftool-2 --set --type bool /desktop/
or gnome-screensaver migrated to gsettings...
it happens to work because the gconf keys are migrated to gsettings on login, the migration binary was buggy in gconf 2.32.4 (which exposed this bug) and is fixed again in 2.32.5
we should change that for a gsettings,dconf use but desrt recommended to way for dconf changes he added to his todolist to be able to create a db without needing to spawn a session bus, the current works until we do it this way, which should be before the lts