confined applications show as unconfined
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-software (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
Applications that are confined, e.g.; chromium (https:/
Screenshots attached.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-software-
Uname: Linux 4.18.20-
ApportVersion: 2.20.10-0ubuntu19
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 25 16:26:54 2019
InstallationDate: Installed on 2019-01-24 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190123)
InstalledPlugins:
gnome-
gnome-
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
I tried this on my 19.04 machine and Chromium is showing as being confined (both when not installed and installed).
There are two things that must be true for G-S to consider a snap to be confined:
1. The snap must be confined:
$ curl --unix-socket /run/snapd.socket http:// localhost/ v2/find? name=chromium|jq .result[ 0].confinement
"strict"
2. snapd must be confined:
$ curl --unix-socket /run/snapd.socket http:// localhost/ v2/system- info|jq .result.confinement
"strict"
Are any of those different in your case?