[Expired for snapd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: snapd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705988
[Expired for juju because there has been no activity for 60 days.]
** Changed in: juju
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705988
Title:
snap
[Expired for snapd because there has been no activity for 60 days.]
** Changed in: snapd
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705988
Title:
snap
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705988
Title:
snap install --classic juju fails
To manage notifications about this bug
I'm switching this bug to incomplete because the last update was over
two years ago. Dear reporter, can you please look at assessing this
issue again? Is it still a problem?
** Changed in: snapd
Status: New => Incomplete
--
You received this bug notification because you are a member of
AIUI there a a few AppArmor patches that have not yet landed upstream,
for confinement. For the rest, vanilla latest upstream should work, most
of the things snapd requires have landed.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Maybe this is related to the fact that I'm running a generic kernel?
(The zesty kernels are unstable on my machine.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705988
Title:
snap install
root@peleg:~# snap version
snap2.26.9
snapd 2.26.9
series 16
ubuntu 17.04
kernel 4.12.0-041200-generic
root@peleg:~# snap list
Name VersionRev Developer Notes
core 16-2.26.9 2381 canonical -
root@peleg:~# snap refresh
All snaps up to date.
No containers were harmed (or used)
If you are installing snaps in an LXD container, you also need to make sure
you have squashfuse installed (and possibly also 'fuse' as there may be a
problem with the dependencies).
They were looking to add those into the default images (since snapd is also
there), but its possible your image is
I think this is related to the lxd container. Can you tell me if it has
apparmor stacking enabled or runs unconfined? The error message (cannot
change profile for the next exec call: No such file or director) seems
to say that snap-confine cannot change the apparmor profile for during
the exec
What is the output of: "snap version" on the system where this fails?
Fwiw, it works fine on my 2.26.14 based machine. So any hint on what I
can do to reproduce is appreciated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** No longer affects: snap (Ubuntu)
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705988
Title:
snap install --classic juju
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705988
Title:
snap install --classic juju fails
To manage notifications
** Also affects: snap (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705988
Title:
snap install --classic juju fails
To manage notifications
14 matches
Mail list logo
