New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timer with WakeSystem=true increases elapse time after system suspend #29245
Comments
WakeSystem= is not supported in --user sessions unless you allow CAP_WAKE_ALARM in your session. Hence what you are asking for here simply has no effect at all. |
Edit: |
@poettering Same behavior when running as system. The system is suspended after the 1st
Edit: Also tried suspending less than 1min and manual wake up, the timer didn't count down either. p.s. No issue when using |
It seems that time change is detected after wake up, which triggers a recalculation of
And Line 471 in 8c5f649
|
systemd version the issue has been seen with
254.2-7.fc39.x86_64
Used distribution
Fedora Workstation 39 Beta
Linux kernel version used
6.5.3-300.fc39.x86_64
CPU architectures issue was seen on
x86_64
Component
systemd-run
Expected behaviour you didn't see
System wakes up and executes the command after timers with
WakeSystem=true
elaspe.LEFT
time of those timers reported bysystemctl list-timers --all --user
decreases after a suspend.Unexpected behaviour you saw
LEFT
time of the timers stayed the same (probably).The system woke up as expected, but then waited
LEFT
time before executing the command.Ref: 1 2 3
Steps to reproduce the problem
systemd-run --collect --user --unit=alarm-clock --on-active="1m" --timer-property=WakeSystem=true flatpak run io.bassi.Amberol
systemctl list-timers --all --user
.Additional program output to the terminal or log subsystem illustrating the issue
The text was updated successfully, but these errors were encountered: