You are not logged in.
Hello. I have a script that is launched by a timer which also wakes up the system (in case it's suspended) on a OnCalendar event.
I enable and start the timer with:
systemctl --user start backup.timer
systemctl --user enable backup.timer
It worked on my previous slightly non-updated arch installtion. Now that I've reinstalled and updated it, it doesn't work anymore and I get the following errors:
...
systemd[1316]: backup.timer: Failed to enter waiting state: Operation not permitted
systemd[1316]: Failed to start run backup.
...
If I remove WakeSystem=true from my .timer file everything works as before, so my questions are:
does the user need special permissions to wake up the system?
If so, how to give them?
Is it a bug (since it worked before) or am I forgetting something?
Joelmo on GitHub seems to have the same issues (Feb 14, 2017), which he solved by disabling the WakeSystem functionality altogether.
Offline
Sounds like a flaw in systemd...I mean, if you can systemctl suspend as a user
Offline
Sounds like a flaw in systemd...I mean, if you can systemctl suspend as a user
Yes,
$ systemctl suspend
works if launched by the unpriviledged user
Offline