This bug was fixed in the package snap-confine -
1.0.38-0ubuntu0.16.04.10
---
snap-confine (1.0.38-0ubuntu0.16.04.10) xenial; urgency=medium
* debian/usr.lib.snapd.snap-confine:
- synchronize apparmor profile with upstream 1.0.40 release.
(LP: #1597842, LP: #1615113, LP:
Per agreement with jdstrand it is sufficient to verify that the new
policy is a superset (that is, it allows to do more, not less) of the
old policy. This prevents the possibility of regressions. Given that the
original bug was reported on a non-common hardware/kernel combination
this serves as a
Yann could you please verify that this bug is fixed by the package in
xenial-proposed?
You can find more information about the process at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: snap-confine (Ubuntu Xenial)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Xenial)
** Changed in: snap-confine (Ubuntu Xenial)
Status: New => In Progress
** Also affects: snap-confine (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snap-confine (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
+ [Impact]
- - Finding issues running snaps (hello-world).
+ snap-confine would refuse to work on an older kernel running on an
+ Nvidia Tegra X1 board. This was traced to a bug in older version of
+ apparmor there that required directory-like syntax for /dev/pts/ptmx
Hello Pedro, or anyone else affected,
Accepted snap-confine into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/snap-
confine/1.0.38-0ubuntu0.16.04.10 in a few hours, and then in the
-proposed repository.
Please help us by testing this new
** Changed in: snap-confine
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1584456
Title:
apparmor denial using ptmx char device
Status in
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1584456
Title:
apparmor denial using ptmx char device
Status in Snappy Launcher:
Fix Committed
Status in linux package in
** Changed in: snap-confine
Milestone: None => 1.0.40
** Changed in: snap-confine
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1584456
https://github.com/snapcore/snap-confine/pull/101
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1584456
Title:
apparmor denial using ptmx char device
Status in Snappy Launcher:
In
Tyler and I discussed this and feel that since this bug is understood
and fixed in newer kernels that adding a workaround rule to the policy
is fine at this point.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Project changed: snappy => snap-confine
** Changed
12 matches
Mail list logo
