Linux Lite Forums
Hardware - Support => Start up and Shutdown => Topic started by: brianread on January 02, 2018, 06:27:55 AM
-
Newly install 3.6 64 bits
I set it to suspend after 30 minutes of no activity, but when it gets there it asks for authentication!
Cheers Brian
-
Here's a screen shot of the dialog.
https://www.dropbox.com/s/d4k9a6s23d94ckx/Screenshot_2018-01-02_14-24-43.png?dl=0
-
Hi @brianread
Looks like screen locker is activated. Check that out in XFCE Power Manager and if so uncheck "Lock the screen when the system is going for sleep".
Hope this helps! :)
-
Hi @brianread
Looks like screen locker is activated. Check that out in XFCE Power Manager and if so uncheck "Lock the screen when the system is going for sleep".
Hope this helps! :)
yes it is - I want the screen to be locked and then suspend subsequently. However I can see that that might not make too much sense - so I'll try it.
What I actually mean is that I want the system to be locked when it is woken up, which I thought is the point of that parameter.
-
What I actually mean is that I want the system to be locked when it is woken up, which I thought is the point of that parameter
Does that message appears right before "sleep" or when waking the system up? Maybe you're setting up power management wrongly?
While googling around I found this: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1605189 which seems to be quite your issue.
-
What I actually mean is that I want the system to be locked when it is woken up, which I thought is the point of that parameter
Does that message appears right before "sleep" or when waking the system up? Maybe you're setting up power management wrongly?
While googling around I found this: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1605189 which seems to be quite your issue.
i comes as it tries to sleep. I've tried gdm and xdm, and both of them sleep sucessfully without the authenticate request, but do not resume properly (which may be a seperate problem). If I suspend manually then the system does resume properly.
Actually I've destroyed my install as I did an "apt-get remove xdm" and it now fails to boot either into the xsession or a terminal session. Am attempting to mend it as we speak using the live CD.
I tried to apply the fix in your link (creating a new file), however the file path did not make sense, perhaps something has changed in the interim?
-
I've now done a new install and out of the box the auto suspend works fine, however once you set the slider "blank after" on the "Display" tab of the Xfce Power manager setting pane, then the authentication comes up when the suspend is requested after the idle timeout.
-
Hi @brianread
I tried to apply the fix in your link (creating a new file), however the file path did not make sense, perhaps something has changed in the interim?
Well, they're talking on Xubuntu so paths might be different.
I've now done a new install and out of the box the auto suspend works fine, however once you set the slider "blank after" on the "Display" tab of the Xfce Power manager setting pane, then the authentication comes up when the suspend is requested after the idle timeout.
That's weird. Maybe you should try a different set up? Instead of 30 minutes try 20 and see how that goes. I've never had problems with that but mine is set up to at 5 minutes of no activity. Tell me your power management configuration so I try here and see what happens.
-
Hi @brianread
I've now done a new install and out of the box the auto suspend works fine, however once you set the slider "blank after" on the "Display" tab of the Xfce Power manager setting pane, then the authentication comes up when the suspend is requested after the idle timeout.
That's weird. Maybe you should try a different set up? Instead of 30 minutes try 20 and see how that goes. I've never had problems with that but mine is set up to at 5 minutes of no activity. Tell me your power management configuration so I try here and see what happens.
I've shipped it to the end user now, it seemed to be the parameter that controlled if it blanked the screen that caused it to try to authenticate. Setting it to "never" made it work ok, any other time caused it to try to authenticate.
-
I've shipped it to the end user now, it seemed to be the parameter that controlled if it blanked the screen that caused it to try to authenticate. Setting it to "never" made it work ok, any other time caused it to try to authenticate.
Glad you solve it. :)