Reports incorrect information when command not in path
Bug #110622 reported by
Thomas Zander
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| command-not-found |
Fix Released
|
High
|
Zygmunt Krynicki | ||
| command-not-found (Ubuntu) |
Fix Released
|
High
|
Michael Vogt | ||
Bug Description
When I type 'modprobe foo' as a normal user I get a suggestion which package I need to install in order to make that command work.
This, naturally, is a wrong diagnosis since the package is always installed but bash just could not find it in the PATH.
Giving wrong information is a really bad idea as the user will end up searching for the wrong solution and IF he ever figures out the real problem (should have used sudo) he will trust his system less.
I consider this a critical bug.
Revision history for this message
| Zygmunt Krynicki (zyga) wrote | #1 |
| Changed in command-not-found: | |
| assignee: | nobody → zkrynicki |
| importance: | Undecided → High |
| status: | Unconfirmed → Confirmed |
Revision history for this message
| Zygmunt Krynicki (zyga) wrote | #2 |
| Changed in command-not-found: | |
| importance: | Undecided → High |
| status: | Unconfirmed → Confirmed |
| status: | Confirmed → Fix Released |
Revision history for this message
| Niklas Klein (kleinernik) wrote | #3 |
Revision history for this message
| Daniel Holbach (dholbach) wrote | #4 |
| Changed in command-not-found: | |
| assignee: | nobody → mvo |
Revision history for this message
| Michael Vogt (mvo) wrote | #5 |
| Changed in command-not-found: | |
| status: | Confirmed → Fix Committed |
| Changed in command-not-found: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Thanks for your bug report. I have never tested this as a non-admin user (without */sbin). This can be fixed for the next release but is probably not fixable for the release found in Ubuntu 7.04 as command-not-found simply has no idea about the full path of an executable.