This turned out to be an issue with some infrastructure that command-not-found uses to map binaries to package names. Nothing to do for systemd.
This turned out to be an issue with some infrastructure that command-not-found uses to map binaries to package names. Nothing to do for systemd.