Comment 10 for bug 1928305

While I waited for reply, I found an appropriate solution.
The cause of the problem was that in the system with lightdm and unity-greeter
installed as a desktop manager and a greeter respectively timeout intervals are
given _twice_ as numeric values:

(1) Time before suspend in lightdm.
(2) Time before suspend in unity-greeter.

To change the first set of parameters (for lightdm) I needed to specify the values for
the user lightdm by means of dconf editor:

sudo -u lightdm dbus-launch gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0
sudo -u lightdm dbus-launch gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0

I also changed the type of action after the suspend time elapses to 'nothing'

sudo -u lightdm dbus-launch gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing'
sudo -u lightdm dbus-launch gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'nothing'

To change the second set of parameters (for unity-greeter) I needed to perform a
similar action:

sudo -u lightdm dbus-launch gsettings set com.canonical.unity.settings-daemon.plugins.power sleep-inactive-ac-timeout 0
sudo -u lightdm dbus-launch gsettings set com.canonical.unity.settings-daemon.plugins.power sleep-inactive-battery-timeout 0

And

sudo -u lightdm dbus-launch gsettings set com.canonical.unity.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing'
sudo -u lightdm dbus-launch gsettings set com.canonical.unity.settings-daemon.plugins.power sleep-inactive-battery-type 'nothing'

Test showed that no further suspend event was observed.

There was no bug, rather simple misunderstanding of that lightdm and unity-greeter store parameters in different places.

With kind regards, Ruben Alexandrovich Iskandaryan.