Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#76173 - [systemd] 251.5-1: OnCalendar-timers not triggered afterwards when system suspended (S3)
Attached to Project:
Arch Linux
Opened by Uhrenvergleich (Uhrenvergleich) - Tuesday, 11 October 2022, 16:34 GMT
Last edited by Christian Hesse (eworm) - Thursday, 20 October 2022, 13:12 GMT
Opened by Uhrenvergleich (Uhrenvergleich) - Tuesday, 11 October 2022, 16:34 GMT
Last edited by Christian Hesse (eworm) - Thursday, 20 October 2022, 13:12 GMT
|
DetailsDescription:
Up to version 251.4-1 OnCalendar-timers for the user daemon were triggered after the system resumes from beeing suspended (S3), when their elapse time was while beeing suspended. With 251.5-1, they are not. The journal shows the same except that the service is not started with 251.5-1. Steps to reproduce: Schedule a service with an OnCalendar-timer in 251.5-1. Suspend the system while this time, resume. The service is not triggered. Do the same in 251.4-1. The service is triggered after resuming from suspend. I downgraded systemd, systemd-libs and systemd-sysvcompat. Thank you! |
This task depends upon
Closed by Christian Hesse (eworm)
Thursday, 20 October 2022, 13:12 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 251.6-2
Thursday, 20 October 2022, 13:12 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 251.6-2
[1] https://github.com/systemd/systemd-stable/commit/37b54927
[2] https://wiki.archlinux.org/title/Bisecting_bugs_with_Git
However, I found https://github.com/systemd/systemd/issues/24984 and completed it.