[Bug 2000753] Re: Snap packages with classic confinement should recommend using `--classic`

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: command-not-found (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to command-not-found in Ubuntu.
https://bugs.launchpad.net/bugs/2000753

Title:
  Snap packages with classic confinement should recommend using
  `--classic`

Status in command-not-found package in Ubuntu:
  Confirmed

Bug description:
  Currently, attempting to run a command from a classic-confined snap
  goes as follows:

  lengau at hyperion:~/Projects/cli$ gitkraken
  Command 'gitkraken' not found, but can be installed with:
  sudo snap install gitkraken
  lengau at hyperion:~/Projects/cli$ sudo snap install gitkraken
  [sudo] password for lengau: 
  error: This revision of snap "gitkraken" was published using classic confinement and thus may
         perform arbitrary system changes outside of the security sandbox that snaps are usually
         confined to, which may put your system at risk.

         If you understand and want to proceed repeat the command including --classic.
  lengau at hyperion:~/Projects/cli$ sudo snap install gitkraken --classic
  gitkraken 9.0.0 from gitkraken✓ installed
  lengau at hyperion:~/Projects/cli$

  Essentially, `command-not-found` is providing a command that requires
  a second attempt before it works. While this does make the user aware
  of the risks of classic-confined snaps, this can be done within the
  output of `command-not-found` instead if needed, still offering a
  better user experience.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/2000753/+subscriptions