Package Details: snapd 2.48-1

Git Clone URL: (read-only, click to copy)
Package Base: snapd
Description: Service and tools for management of snap packages.
Upstream URL:
Licenses: GPL3
Conflicts: snap-confine
Submitter: Barthalion
Maintainer: bboozzoo (zyga)
Last Packager: bboozzoo
Votes: 136
Popularity: 4.50
First Submitted: 2018-01-07 17:37
Last Updated: 2020-11-23 10:01

Pinned Comments

bboozzoo commented on 2018-10-25 11:56

2.36 is the first release with AppArmor enabled by default on Arch.

If you do not have AppArmor enabled at boot there should be no functional changes visible.

If you wish to use snaps with Apparmor, first make sure that Apparmor is enabled during boot, see for details. After upgrading the package, you need to do the following steps:

  • Reload the profiles: systemctl restart apparmor.service
  • Restart snapd: systemctl restart snapd.service
  • Load profiles for snaps: systemctl enable --now snapd.apparmor.service

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 ... Next › Last »

bboozzoo commented on 2019-11-05 15:42

@archplayer this should be fixed now with the latest update to 2.42.1.

bboozzoo commented on 2019-11-04 12:37

@archplayer would it be possible for you to provide the output of eu-readelf -n /usr/lib/snapd/snap-seccomp ? eu-readelf is part of elfutils package.

If that's easier, then readelf -n /usr/lib/snapd/snap-seccomp output is fine too.

zyga commented on 2019-11-01 10:38

The issue reported by @archplayer is now tracked as

archplayer commented on 2019-11-01 01:34

Hi. Ever since end of May 2019, snappy daemon fails to start on my system (with or without apparmor). This is what I see in the output of

$ sudo journalctl -u snapd.service
cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: invalid format of version-info: "6f33567a6d5533534e6273424138556e5a7757582f654153436e383650336a61346537544b673975482f565059786473696e77496b3275724a39755f6d6d2f48314d544863384d51344c417a4c387845717976 2.4.1 8c73f36d3de1f71977107bf6687514f16787f639058b4db4c67b28dfdb2fd3af bpf-actlog"]

bboozzoo commented on 2019-10-22 08:27

@malathion is there anything in dmesg that would suggest AppArmor blocked it? Anything in journalctl -u snapd? Does uname -r list the same kernel version as reported by pacman -Q linux?

malathion commented on 2019-10-22 08:20

$ sudo snap install <thing>
error: system does not fully support snapd: cannot mount squashfs image using "squashfs": mount:
       /tmp/sanity-mountpoint-581485990: mount failed: Operation not permitted.

bboozzoo commented on 2019-10-17 08:57

@landaro do you have a log perhaps? Are you sure this isn't your AUR helper? There's no dependency on netcat (either variant), so I'm not sure how you got there. It builds and installs just fine if nc isn't available.

landaro commented on 2019-10-17 08:50

I believe there might be a missing dependency on netcat with this package. My initial installation attempt failed with a command not found: nc. Manually installing one of the providers for nc fixed the problem, though.

dharrigan commented on 2019-10-05 20:43


Thanks for fixing! Yes, GO111MODULES was set to on. I've disabled it (or rather, put it to the default behaviour of auto).

Thank you for being responsive :-)


bboozzoo commented on 2019-10-05 13:27

@dharrigan that's a bit surprising, snapd does not use go.mod. Is it possible that you have GO111MODULE=on in your environment?

Edit: yeah, I was able to reproduce this problem by setting GO111MODULE=on in my environment. I've pushed an update.