It looks like the global need-reload state that Christian investigated that is being set by a snapd operation was added recently in systemd.
https://github.com/systemd/systemd/commit/a82b8b3dc80619c3275ad8180069289b411206d0 That is likely why we're only seeing this issue in noble. From reading the commit message there, it sounds like the right thing to do is for snapd to issue a daemon-reload after it sets up all its units. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055239 Title: Warning: The unit file, source configuration file or drop-ins of {apt- news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2055239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
