Entering an excessively long command causes command-not-found to crash

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

Bug Description

Entering an excessively long command that doesn't exist crashes command-not-found. I opened up a terminal in Ubuntu and pasted a long string of a few thousand "a"s, and got this error.

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.44

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.