Inconsistent error message when installing multiple classic snaps
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| snapd |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Installing a single snap which requires classic, while not specifying that we need classic results in a useful message and details of what to do next..
alan@deep-
error: This revision of snap "goland" 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.
Installing multiple snaps, where some may need the classic parameter specified - do not. They spit out a list and no information about what to do next. This is inconsistent. It should probably produce a list of snaps and similar text to above.
alan@deep-
error: cannot install ["goland" "intellij-
"phpstorm" "micro" "webstorm" "atom" "writeful" "hiri" "wavebox"
"corebird" "mattermost-
"doctl" "task" "packager" "sentry" "osddm" "fades"]: snap "goland"
requires classic confinement
| Changed in snapd: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Michael Vogt (mvo) wrote | #1 |
| Changed in snapd: | |
| status: | Triaged → Fix Committed |
| Changed in snapd: | |
| status: | Fix Committed → Fix Released |
I pushed a fix to https:/
With that I get:
sudo ./snap install hello goland intellij-
error: This revision of snap "goland" 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.
I.e. it will stop after the first snap that fails to install. But that should be ok as you can then iterate on it.