I've changed the title to "command-not-found can't be removed properly using apt," after realizing that this isn't just an issue with upgrading after removing the package. Actually it appears that on any system running lucid, doing an "apt-get remove command-not-found" leaves the shell in the broken state described above.
** Summary changed: - [lucid] command-not-found in broken state after upgrade + [lucid] command-not-found can't be removed properly using apt -- [lucid] command-not-found can't be removed properly using apt https://bugs.launchpad.net/bugs/561046 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
