Comment 1 for bug 1687079

This was fixed in master and has been merged into the snapd 2.25 release.

If you switch to the beta channel you can confirm that it is fixed for you.

Try this command: snap refresh core --beta

Having said that, can you tell me more about your environment. This
issue should never occur if you are using the Ubuntu kernel with
apparmor enabled. Are you using a different kernel or have you
explicitly disabled apparmor on boot?

On Fri, Apr 28, 2017 at 7:39 PM, hackel <email address hidden> wrote:
> Public bug reported:
>
> I am unable to run any snaps. I installed hello and when I run `snap
> run hello` I get:
>
> "cannot change profile for the next exec call: No such file or
> directory"
>
> The same message appears with any snap that I run.
>
> I'm using Ubuntu 17.04, so I don't believe it's the same issue as
> #1662899, but could be related.
>
> ** Affects: snappy
> Importance: Undecided
> Status: New
>
> ** Description changed:
>
> I am unable to run any snaps. I installed hello and when I run `snap
> run hello` I get:
>
> "cannot change profile for the next exec call: No such file or
> directory"
>
> - The same message appears with any spap that I run.
> + The same message appears with any snap that I run.
>
> I'm using Ubuntu 17.04, so I don't believe it's the same issue as
> #1662899, but could be related.
>
> --
> You received this bug notification because you are a member of Snappy
> Developers, which is subscribed to Snappy.
> Matching subscriptions: xxx-bugs-on-snapd
> https://bugs.launchpad.net/bugs/1687079
>
> Title:
> cannot change profile for the next exec call: No such file or
> directory
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/snappy/+bug/1687079/+subscriptions