light-locker-settings reverts to "never" after reboot.

Hi, can you give me a bit more information? Are you using Ubuntu, Lubuntu, Xubuntu, something else?

I can confirm this issue on Arch Linux. Here is the traceback:

Traceback (most recent call last):
  File "/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py", line 176, in apply_cb
    self.apply_settings()
  File "/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py", line 629, in apply_settings
    self.apply_screen_blank_settings(settings)
  File "/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py", line 691, in apply_screen_blank_settings
    keyfile = self.get_screensaver_autostart()
  File "/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py", line 400, in get_screensaver_autostart
    self.get_autostart('screensaver-settings.desktop', defaults)
  File "/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py", line 358, in get_autostart
    GLib.KeyFileFlags.KEEP_TRANSLATIONS)
GLib.Error: g-key-file-error-quark: Valid key file could not be found in search dirs (2)

I can also confirm this behaviour on Arch Linux. Light-Locker-Setting will not store the changed settings after they are applied.

The problem is that light-locker-settings fails if the expected file does not already exist. There is a simple workaround by creating an empty file in that location before launching light-locker-settings:

    $ touch ~/.config/autostart/screensaver-settings.desktop
    $ light-locker-settings

I am also attaching a patch that kind of solves this problem by masking any error that the load function might raise. I do not really understand the GLib python bindings here, though. Apparently it is supposed to return an error code, but at the same time it always raises a generic GLib.Error, so the return value cannot be checked at all...?

The attachment "light-locker-settings-ignore-error.diff" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]