I believe the problem is that the user-specific .desktop file, ``~/.config/autostart/light-locker.desktop`` does not override the the system wide .desktop file ``/etc/xdg/autostart/light-locker.desktop``.
When the user changes the light-locker settings to disable light-locker, I believe what happens is that ``~/.config/autostart/light-locker.desktop`` is edited/created so the there is a blank ``Exec=`` line. That is, light-locker is not started.
However, even if light-locker is disabled in the user-specific file, it is still started (with the default configuration) by the system-wide light-locker.desktop file.
The workaround that worked for me was to rename ``/etc/xdg/autostart/light-locker.desktop`` to ``/etc/xdg/autostart/light-locker.desktop.bak``.
I believe the problem is that the user-specific .desktop file, ``~/.config/ autostart/ light-locker. desktop` ` does not override the the system wide .desktop file ``/etc/ xdg/autostart/ light-locker. desktop` `.
When the user changes the light-locker settings to disable light-locker, I believe what happens is that ``~/.config/ autostart/ light-locker. desktop` ` is edited/created so the there is a blank ``Exec=`` line. That is, light-locker is not started.
However, even if light-locker is disabled in the user-specific file, it is still started (with the default configuration) by the system-wide light-locker. desktop file.
The workaround that worked for me was to rename ``/etc/ xdg/autostart/ light-locker. desktop` ` to ``/etc/ xdg/autostart/ light-locker. desktop. bak``.