[Bug 966010] Re: /etc/bash.bashrc checks for command-not-found OR command-not-found-data

[Andrew McCarthy]

*** This bug is a duplicate of bug 561046 ***
    https://bugs.launchpad.net/bugs/561046

Thanks for taking the time to report this.

I believe this is the same as bug #561046 (Debian bug 529313) which has
been fixed in precise, due for final release next week.


** This bug has been marked a duplicate of bug 561046
   [lucid] command-not-found can't be removed properly using apt

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/966010

Title:
  /etc/bash.bashrc checks for command-not-found OR command-not-found-
  data

Status in “bash” package in Ubuntu:
  New

Bug description:
  /etc/bash.bashrc checks for two paths to detect command-not-found
  script: /usr/lib/command-not-found OR /usr/share/command-not-found;
  and as consequence when command-not-found package is not installed and
  command-not-found-data IS installed, every time the command-not-found
  code is triggered we get an error:

  /usr/bin/python: can't find '__main__' module in '/usr/share/command-
  not-found'

  I guess command-not-found should be required by command-not-found-
  data, but /etc/bash.bashrc should test path1 AND path2 (instead of
  OR).

  If both command-not-found and command-not-found-data are not
  installed, bash.bashrc code works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/966010/+subscriptions