[Ubuntu 22.04] Auto tab completion does not work with nvme commands.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bash-completion (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Invalid
|
Undecided
|
Unassigned | ||
Kinetic |
Invalid
|
Undecided
|
Unassigned | ||
nvme-cli (Ubuntu) |
Fix Released
|
Medium
|
Benjamin Drung | ||
Jammy |
Fix Released
|
Medium
|
Unassigned | ||
Kinetic |
Fix Released
|
Medium
|
Unassigned |
Bug Description
[ Impact ]
Tab completion for the nvme command is completely broken in bash.
[ Test Plan ]
1. Install nvme-cli package
2. Open terminal
3. type any nvme command and hit tab
Tab completion should show entries like "list", "create-ns", etc.
[ Where problems could occur ]
The patch only changes the tab completion for nvme, but rebuilding nvme-cli can reveal bugs on package upgrade, etc.
[ Original report ]
Description:
On pressing tab with nvme command, it shows the hostname instead of listing subcommands on Ubuntu 22.04 LTS.
Steps to reproduce:
Step 1: Install Ubuntu 22.04 LTS (ubuntu-
Step 2: Install nvme-cli package,currently installed version is nvme version 1.16
Step 3: In the os terminal, type any nvme command and hit tab, auto tab completion is not working properly.
Expected Behavior:
Upon pressing tab, nvme command should show the supported subcommands.
information type: | Public → Private |
information type: | Private → Public |
Changed in bash-completion (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in nvme-cli (Ubuntu Jammy): | |
status: | Confirmed → Triaged |
Changed in nvme-cli (Ubuntu Kinetic): | |
status: | Confirmed → Triaged |
tags: | added: foundations-todo |
tags: | added: patch |
description: | updated |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1980820
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.