Ubuntu
command-not-found package

command-not-found claims bootctl can be installed with `sudo apt install systemd`

Bug #1996820 reported by TomasHnyk
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
command-not-found (Ubuntu)
New
Low
Unassigned
systemd (Ubuntu)
Invalid
Low
Unassigned

Bug Description

On a fresh 22.10 install, I tried to install systemd-boot by running bootctl. I get a message saying

"
Command 'bootctl' not found, but can be installed with:
sudo apt install systemd
"

But actually the package to install is systemd-boot.

Revision history for this message
Nick Rosbrook (enr0n) wrote :

The command-not-found package is responsible for showing that information. I'm not sure how the internals work though, so it's possible there's something wonky with the systemd package that confuses command-not-found.

Changed in systemd (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Changed in command-not-found (Ubuntu):
importance: Undecided → Low
summary: - When running bootctl, wrong promt is displayed
+ command-not-found claims bootctl can be installed with `sudo apt install
+ systemd`
Revision history for this message
Nick Rosbrook (enr0n) wrote :

This turned out to be an issue with some infrastructure that command-not-found uses to map binaries to package names. Nothing to do for systemd.

Changed in systemd (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.