command-not-found crashes on russian characters (utf8) input

Bug #851078 reported by Anton Novikov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
command-not-found
New
Undecided
Unassigned

Bug Description

user@host:~$ хуй
Sorry, command-not-found has crashed! Please file a bug report at:
https://bugs.launchpad.net/command-not-found/+filebug
Please include the following information with the report:

command-not-found version: 0.2.21

Revision history for this message
Anton Novikov (an146) wrote :

possible fix could be just never trying to handle utf8 input, for me it's usually caused by typing in wrong keyboard layout, so command-not-found just can't do anything sane about the input

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.