[Bug 466397] New: after removing command-not-found, running shells stop reporting "command not found"
https://bugzilla.novell.com/show_bug.cgi?id=466397 Summary: after removing command-not-found, running shells stop reporting "command not found" Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: prusnak@novell.com ReportedBy: mmarek@novell.com QAContact: qa@suse.de CC: mvyskocil@novell.com Found By: --- After removing the command-not-found package, running bash sessions stop reporting "bash: xyz: command not found": $ xyz; echo $? 1 $ command -V command_not_found_handle command_not_found_handle is a function command_not_found_handle () { if [ -n "$MC_SID" ]; then return 127; fi; [ -x /usr/bin/python ] && [ -x /usr/bin/command-not-found ] && /usr/bin/python /usr/bin/command-not-found "$@" zypp } it should return 127 if the program is not available. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466397 User prusnak@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=466397#c1 Pavol Rusnak <prusnak@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |ast@novell.com --- Comment #1 from Pavol Rusnak <prusnak@novell.com> 2009-01-15 07:27:42 MST --- Fixed line to [ -x /usr/bin/python ] && [ -x /usr/bin/command-not-found ] && /usr/bin/python /usr/bin/command-not-found "$@" zypp || return 127 Should do the trick. Anja: are we going to release update for 11.1 ? It only affects shells that were open during the removal of the package. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466397 User prusnak@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=466397#c3 Pavol Rusnak <prusnak@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #3 from Pavol Rusnak <prusnak@novell.com> 2009-01-15 08:05:11 MST --- Michal: fix is in Comment#1, or you can install fixed command-not-found package from home:prusnak:scout. Thanks for the report! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466397 User mmarek@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=466397#c4 --- Comment #4 from Michal Marek <mmarek@novell.com> 2009-01-15 08:13:34 MST --- unset command_not_found_handle in the few xterms worked fine for me. I didn't intend to request an online update :). Thanks for the fix. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466397 User prusnak@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=466397#c5 --- Comment #5 from Pavol Rusnak <prusnak@novell.com> 2009-01-15 08:18:01 MST --- Yes, that's another option, but this only fixes consequence, not the cause of the problem. :) PS: I hope that you removed the command-not-found package only to discover this bug and you are installing it back. *grin* -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com