Wrong language settings may crash command-not-found handler
Bug #1073301 reported by
rpkrawczyk
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
command-not-found |
New
|
Undecided
|
Unassigned |
Bug Description
The following happens:
$ §
§: command not found
That is OK. Now:
$ unset LANG
$ §
Sorry, command-not-found has crashed! Please file a bug report at:
https:/
Please include the following information with the report:
command-not-found version: 0.2.44
The important thing is that *any* non ASCII character in the command name will cause a crash. I would have expected to have an error message (maybe garbled) but not a crash. BTW, calling command-not-found directly also results in a crash after unsetting LANG, e.g. "/usr/lib/
To post a comment you must log in.
OK, is this the same problem as in #887502?