Removing command-not-found results in error

Bug #194939 reported by Bruce Cowan
8
Affects Status Importance Assigned to Milestone
bash (Ubuntu)
Fix Released
Low
Michael Vogt
command-not-found (Ubuntu)
Fix Released
Low
Michael Vogt

Bug Description

Binary package hint: bash

Removing command-not-found and then trying a program that isn't installed results in an error:

/usr/bin/python: can't open file '/usr/lib/command-not-found': [Errno 2] No such file or directory

Related branches

Revision history for this message
unksi (unksi) wrote :

Confirmed, happens on fully updated Hardy.

Changed in bash:
status: New → Confirmed
Revision history for this message
Kjell Braden (afflux) wrote :

Happens only on shells present before the removal. Using command-not-found 0.2.12ubuntu1

Changed in bash:
assignee: nobody → afflux
importance: Undecided → Low
status: Confirmed → In Progress
Revision history for this message
Kjell Braden (afflux) wrote :

Assigning to command-not-found as bash can't check if loaded scripts still exist. Rather should the loaded script check if it should run.

Revision history for this message
Kjell Braden (afflux) wrote :

Oh, bash has it's own integration script which should be adjusted, added the bash task. Command-not-found must be adjusted for zsh, though.

Changed in bash:
assignee: nobody → afflux
importance: Undecided → Low
status: New → In Progress
Revision history for this message
Kjell Braden (afflux) wrote :

Debdiff against command-not-found 0.2.12ubuntu1 introducing a check in the command-not-found handler

Revision history for this message
Kjell Braden (afflux) wrote :

Debdiff against bash 3.2-0ubuntu14 introducing a check in the command-not-found handler

Changed in bash:
assignee: afflux → nobody
status: In Progress → Triaged
Changed in command-not-found:
assignee: afflux → nobody
status: In Progress → Triaged
Michael Vogt (mvo)
Changed in bash:
assignee: nobody → mvo
status: Triaged → Fix Committed
Changed in command-not-found:
assignee: nobody → mvo
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bash - 3.2-0ubuntu15

---------------
bash (3.2-0ubuntu15) hardy; urgency=low

  * Don't run command-not-found from the shell scripts when it has been
    removed in the meantime (LP: #194939)

 -- Kjell Braden <email address hidden> Sun, 24 Feb 2008 12:01:31 +0100

Changed in bash:
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package command-not-found - 0.2.15ubuntu1

---------------
command-not-found (0.2.15ubuntu1) hardy; urgency=low

  [ Kjell Braden ]
   * Don't run command-not-found from the shell scripts when it has been
     removed in the meantime (LP: #194939)

  [ Michael Vogt ]
  * CommandNotFound/CommandNotFound.py:
    - do not advise on ".." (LP: # 195090) - thanks to Thomas Perl
    - do not crash on problems with python-apt (LP: #161804)
  * debian/control:
    - improve description (LP: #144153)
  * command-not-found:
    - make the crash message a bit more friendly
  * use lgettext() instead of gettext() (LP: #161159)

 -- Michael Vogt <email address hidden> Fri, 07 Mar 2008 10:01:20 +0100

Changed in command-not-found:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.