Trying to run any snap apps

Kaverdinho · February 11, 2019, 11:22pm

Hello, whenever i try to run any app i get an error.

I’ve read most topics i could find on this but with no solution. i am using version

version 2.37.1

Thanks for the quick replay. I’m using snap 2.37.1 snapd 2.37.1 series 16 kali 2019.1 kernel 4.18.0-kali2-amd64

here is some systemctl status outputs.

systemctl status snapd

root@kali:~# systemctl status snapd ● snapd.service - Snappy daemon Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: di Active: active (running) since Mon 2019-02-11 23:02:03 UTC; 12min ago Main PID: 12123 (snapd) Tasks: 11 (limit: 4915) Memory: 37.9M CGroup: /system.slice/snapd.service └─12123 /usr/lib/snapd/snapd

Feb 11 23:02:02 kali systemd[1]: Starting Snappy daemon… Feb 11 23:02:03 kali snapd[12123]: AppArmor status: apparmor is enabled but some Feb 11 23:02:03 kali snapd[12123]: AppArmor status: apparmor is enabled but some Feb 11 23:02:03 kali snapd[12123]: backend.go:126: snapd enabled root filesystem Feb 11 23:02:03 kali snapd[12123]: daemon.go:379: started snapd/2.37.1 (series 1 Feb 11 23:02:03 kali systemd[1]: Started Snappy daemon.

systemctl status apparmor

root@kali:~# systemctl status apparmor ● apparmor.service - Load AppArmor profiles Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: Active: active (exited) since Mon 2019-02-11 20:25:34 UTC; 2h 52min ago Docs: man:apparmor(7) https://gitlab.com/apparmor/apparmor/wikis/home/ Main PID: 5202 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) Memory: 0B CGroup: /system.slice/apparmor.service

Feb 11 20:25:34 kali systemd[1]: Starting Load AppArmor profiles… Feb 11 20:25:34 kali apparmor.systemd[5202]: Restarting AppArmor Feb 11 20:25:34 kali apparmor.systemd[5202]: Reloading AppArmor profiles Feb 11 20:25:34 kali systemd[1]: Started Load AppArmor profiles.

This is what happens when i try to run spotify

snap run spotify

root@kali:~# snap run spotify cannot create lock directory /run/snapd/lock: Permission denied

i’m using kali 64bit i’ve already done sudo apt update

and

sudo apt upgrade

please let me know if you need additional information because i’ve looked everywhere and did all sorts of things

chipaca · February 12, 2019, 1:19am

What’s the output of snap version?

Kaverdinho · February 12, 2019, 3:55am

Thanks for the quick replay.
I’m using
snap 2.37.1
snapd 2.37.1
series 16
kali 2019.1
kernel 4.18.0-kali2-amd64

Kaverdinho · February 13, 2019, 5:48pm

I have also tried going to the directory, /run/ and changed permissions for the folder, but there is no change.
i looked for a folder called snapd inside the /run/ directory but there was none, so i made it and gave full permission to root and also made a directory inside the /run/snapd/ called lock but still no change, any ideas?

chipaca · February 13, 2019, 8:18pm

I can confirm this is happening on kali linux.
I’m not sure if it’s related, but in dmesg I see

[  356.733283] audit: type=1400 audit(1550088905.732:21): apparmor="DENIED" operation="open" profile="/usr/lib/snapd/snap-confine" name="/rw/" pid=13169 comm="snap-confine" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

zyga-snapd · February 14, 2019, 9:19am

What is the /rw directory?

chipaca · February 14, 2019, 9:25am

Nothing that I can see. But my test was in the live cd, so maybe it’s related to that.

zyga-snapd · February 14, 2019, 9:26am

Support for various live CD environments is limited. This is likely the cause of that.

chipaca · February 14, 2019, 11:15am

@Kaverdinho I installed Kali, and the error went away.

Kaverdinho · February 14, 2019, 1:18pm

@chipaca and @zyga-snapd you guys are awesome thanks for looking into this i really appreciate it!
@chipaca what do you mean you installed kali and it went away? i have installed kali on a external Seagate HDD connected with a USB3 is that not enough? does it have to be installed to a SSD/HDD connected through the SATA connection?

chipaca · February 14, 2019, 1:20pm

as long as it’s not a live CD, the problem I saw should not be there. Do you see any denials in your dmesg?

Kaverdinho · February 14, 2019, 1:36pm

not really, i do see some reds but im not sure its related

Reds

[ +0.000391] platform MSFT0101:00: failed to claim resource 1: [mem 0xfed40000-0xfed40fff]
[ +0.000095] acpi MSFT0101:00: platform device creation failed: -16
[ +0.000033] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ IBUS ]
[ +0.013321] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ]
[ +0.000003] nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid
[ +0.572490] ath10k_pci 0000:03:00.0: firmware: failed to load ath10k/pre-cal-pci-0000:03:00.0.bin (-2)
[ +0.008861] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[ +0.008989] ath10k_pci 0000:03:00.0: firmware: failed to load ath10k/cal-pci-0000:03:00.0.bin (-2)
[ +1.899876] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ IBUS ]

zyga-snapd · February 14, 2019, 1:50pm

Tip: dmesg | grep DENIED or journalctl | grep DENIED

Kaverdinho · February 14, 2019, 2:00pm

smarter everyday, thank you. it came back empty with both inputs

EDIT: I am tempted to make a clean install as a 32bit but i would like to avoid it. i have set this environment how i like it and i have let it update for almost a decade

chipaca · February 14, 2019, 4:06pm

hm, I tried the 64 bit one. Should I try with 32?