This seems to happen if the system is in a "restart-needed" state before "update-manager --no-update" is called, as would happen if someone (like me) mixes and matches their apt-get and update-manager usage.
This seems to happen if the system is in a "restart-needed" state before "update-manager --no-update" is called, as would happen if someone (like me) mixes and matches their apt-get and update-manager usage.