Public bug reported: The bug has been reported upstream: https://github.com/systemd/systemd/issues/31231
It's been fixed in: https://github.com/systemd/systemd/pull/38868/changes/3fc44a0f68412b649e16f12ff2f97a36c615457d Need to backport this fix to Questing, Noble, and possibly Jammy too. ** Affects: systemd (Ubuntu) Importance: Undecided Assignee: Ioana Lazea (ioanalazea) Status: New ** Affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Noble) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Questing) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Resolute) Importance: Undecided Assignee: Ioana Lazea (ioanalazea) Status: New ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Ioana Lazea (ioanalazea) ** Also affects: systemd (Ubuntu Questing) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Resolute) Importance: Undecided Assignee: Ioana Lazea (ioanalazea) Status: New ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2141296 Title: [00427578] Restarting systemd timer triggers service start off- schedule To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2141296/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
