Am 08.11.2017 um 20:21 schrieb Alberto Manzaneque García: > I have the same problem too on version 234. > Do you know if there is a systemd (not debian) bug open? > > On Sat, 25 Feb 2017 16:35:20 +0200 (EET) Madis Janson <ma...@cyber.ee > <mailto:ma...@cyber.ee>> wrote: >> >> I have exactly the same problem with Debian Stretch (testing) on amd64. >> Package version is 232-15. >> >> $ systemctl --version >> systemd 232 >> +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP >> +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN >> >> The system wakes, but the service unit won't be started. If the system >> wasn't syspended then the timer service works as expected. >>
Upstream only tracks the latest two upstream releases, but as Alberto can apparently reproduce it with v234 it should be ok to file this upstream at https://github.com/systemd/systemd If you can verify it with v235, even better. Once you have a bug number, please report back and will link the two bug reports then. Thanks, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
