Can’t start a snap app

[yustnip]

I installed as a snap Atom and Corebird and I can't start them. Nothing happens.

--

If I start Atom from CLI I get following:

cannot create lock directory /run/snapd/lock: Permission denied

--

journalctl output:

May 23 23:51:19 Dell-XPS atom[2965]: cmd.go:114: DEBUG: not restarting into "/snap/core/current/usr/bin/snap" ([VERSION=2.24 2.24]): older than "/usr/bin/snap" (2.25+17.04)
May 23 23:51:19 Dell-XPS audit[2965]: AVC apparmor="DENIED" operation="mkdir" profile="/usr/lib/snapd/snap-confine" name="/run/snapd/lock/" pid=2965 comm="snap-confine" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
May 23 23:51:19 Dell-XPS kernel: audit: type=1400 audit(1495572679.568:43): apparmor="DENIED" operation="mkdir" profile="/usr/lib/snapd/snap-confine" name="/run/snapd/lock/" pid=2965 comm="snap-confine" requested_mask="c" denied_mask="c"

[Zygmunt Krynicki (zyga)]

Hello. Can you please ensure that your system is fully up-to-date? In a terminal please run the following command:

sudo dpkg --configure -a

We saw some issues where a partial upgrade happens and new snapd is unpacked but not configured yet.

[yustnip (yustnip)]

Ran this command now. Nothing outputted. Seems all's OK with it.

[Bob W. Hogg (rwhogg)]

Nothing outputted for me either, but that doesn't seem to fix the issue for me.

[yustnip (yustnip)]

Sorry for my English. Yes, the issue is not fixed for me too.

[kevin wiley (beasmygodam)]

i am having this issue aswell. i did have some problems upgrading my system. i am having the problem with a different application and when i sudo dpkg --configure -a nothing happens. i even tried it on snapd its self and it just tells me its already installed and configured

[Thomi Richards (thomir-deactivatedaccount)]

Hi,

I've also just encountered this issue.

Snaps were working fine last week, but this morning every snap I try and run produces the following output:

cannot create lock directory /run/snapd/lock: Permission denied

The following lines are written to syslog:

Jul 3 09:07:59 thinkpad what-snap[3910]: cmd.go:114: DEBUG: not restarting into "/snap/core/current/usr/bin/snap" ([VERSION=2.24 2.24]): older than "/usr/bin/snap" (2.25+17.04)
Jul 3 09:07:59 thinkpad kernel: [303712.032269] audit: type=1400 audit(1499029679.954:251): apparmor="DENIED" operation="mkdir" profile="/usr/lib/snapd/snap-confine" name="/run/snapd/lock/" pid=3910 comm="snap-confine" requested_mask="c" denied_mask="c" fsuid=0 ouid=0

I've run `sudo dpkg --configure -a` as suggested above, but I have no unconfigured packages, so it doesn't do anything.

My core snap is version 16-2 (revision 1689), and the host snapd package is version 2.25+17.04.

[Thomi Richards (thomir-deactivatedaccount)]

For anyone else following along at home, there are some suggestions regarding how to fix this (that worked for me) at:

https://forum.snapcraft.io/t/test-failures-with-cannot-create-lock-directory-run-snapd-lock/390/30

[SaltyCybernaut (saltycybernaut)]

After a generic system upgrade around 7/5 I too experienced this problem with snapd (version: 2.25 on 16.04.02): "cannot create lock directory /run/snapd/lock: Permission denied"

the advice from https://forum.snapcraft.io/t/test-failures-with-cannot-create-lock-directory-run-snapd-lock/390/30 worked for me, specifically running "apparmor_parser --replace --write-cache /etc/apparmor.d/usr.lib.snapd.snap-confine.real --cache-loc /etc/apparmor.d/cache" as root.

[Maciej Borzecki (maciek-borzecki)]

Does the problem persist with recent versions of snapd 2.29/2.30?

[Launchpad Janitor (janitor)]

[Expired for Snappy because there has been no activity for 60 days.]