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:
For the record: the tested version was 1.0.38-0ubuntu0.16.04.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612684
Title:
dies when run in a place that is not inside the snap chroot
To manage
I just verified this on a Xenial VM, following this process
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification
The pre-update version contained a small change that moved the process
to /tmp instead of exiting. With the update installed the process was
correctly moved to /var/lib/snapd/void.
** Description changed:
+ [Impact]
+
+ Snap applications would refuse to run if the current working directory
+ was impossible to preserve across the chroot that snap-confine performs
+ internally.
+
+ This was somewhat annoying and surprising to various users so it was
+ changed to a more
** Changed in: snap-confine (Ubuntu Xenial)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612684
Title:
dies when run in a place that is not inside the
Hello Michael, 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.9 in a few hours, and then in the
-proposed repository.
Please help us by testing this new
This bug was fixed in the package snap-confine - 1.0.38-0ubuntu0.16.04.8
---
snap-confine (1.0.38-0ubuntu0.16.04.8) xenial; urgency=medium
* debian/patches/04_not_die_unknown_locations.patch:
- move to /tmp if the current location can not be preserved
(LP: #1612684)
This is fixed with the 1.0.40 upload to yakkety
** Changed in: snap-confine (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612684
Title:
dies when run
** Changed in: snap-confine
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612684
Title:
dies when run in a place that is not inside the snap chroot
To
This is fixed in master with this patch:
https://github.com/snapcore/snap-
confine/commit/1ab8e095195d07c766f75f85d9d9430a0f088dbd
It will be released as a part of snap-confine 1.0.40
** Also affects: snap-confine
Importance: Undecided
Status: New
** Changed in: snap-confine
Works with latest snap-confine:
fgimenez@innsmouth:~$ apt-cache policy snap-confine
snap-confine:
Installed: 1.0.38-0ubuntu0.16.04.8
Candidate: 1.0.38-0ubuntu0.16.04.8
Version table:
*** 1.0.38-0ubuntu0.16.04.8 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64
** Description changed:
When running any snap from a place that is not inside the snap chroot
(like /tmp/some-subdir or /srv) running the snap-confine launcher dies
with a ugly error.
+
+ TEST CASE:
+ 1. mkdir /tmp/99
+ 2. cd /tmp/99
+ 3. sudo snap install hello-world
+ 4. verify that it
Hello Michael, 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.8 in a few hours, and then in the
-proposed repository.
Please help us by testing this new
13 matches
Mail list logo
