Fixed in precise.
bash (4.2-2) unstable; urgency=low
* Fix command-not-found location. Closes: #529313.
* Print a replacement error message if command-not-found was removed
after bashrc was loaded. Closes: #631023. LP: #561155.
* skel.bashrc: Document and prepare enabling the globstar f
** Changed in: bash (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/561046
Title:
[lucid] command-not-found can't be removed properly using apt
To mana
** Bug watch added: Debian Bug tracker #529313
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529313
** Also affects: bash (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529313
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
If a directory isn't altered, then apt-get purge should remove it. As
it is, /usr/share/command-not-found is left around even after an
uninstall and a subsequent purge.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Interesting info, Thangalin -- thanks for posting that!
So I guess the way I would state the problem now is that if you do an
apt-get remove command-not-found, without removing command-not-found-
data, you put your system in a state where its behavior is broken. I
don't understand why these would
After removing "command-not-found-data":
$ asdf
$ asdfqweri83214987
$ zxcv0987asdf0987324
$ d0987xzcv0987safd0987fdsa
$ kjfdsajfdsa;
This should revert to its former behaviour that says, plainly and
simply, "Command not found", rather than nothing.
--
[lucid] command-not-found can't be removed
Only half of bug 561155 was a duplicate of this. I repurposed that bug
for the other half (if both command-not-found and command-not-found-data
are uninstalled, but a shell remains open, bad commands show no errors
at all) and unmarked it as duplicate.
--
[lucid] command-not-found can't be remov
Thanks, David Leon, for the info. Zygmunt Krynicki, does the patch
described in #4 fix this, or does something else need to be done to fix
this bug?
--
[lucid] command-not-found can't be removed properly using apt
https://bugs.launchpad.net/bugs/561046
You received this bug notification because y
As a workaround, just remove command-not-found-data and things work
fine.
For some reason it's marked as installed manually so it's not removed
when you remove command-not-found.
--
[lucid] command-not-found can't be removed properly using apt
https://bugs.launchpad.net/bugs/561046
You received
I pushed a fix in my branch, it's linked to this bug
--
[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
ubu
** Branch linked: lp:~zkrynicki/bash/lp561046
--
[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-bug
Confirmed
Actually this is a bash bug. See /etc/bash.bashrc
# if the command-not-found package is installed, use it
if [ -x /usr/lib/command-not-found -o -x /usr/share/command-not-found ]; then
function command_not_found_handle {
# check because c-n-f could've been removed
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 broke
13 matches
Mail list logo
