Package Details: snapd 2.51.1-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: 163
Popularity: 4.70
First Submitted: 2018-01-07 17:37
Last Updated: 2021-06-28 07:58

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 ... Next › Last »

dmp1ce commented on 2020-12-11 00:01

@bboozzoo: Thanks for looking into this.

bboozzoo commented on 2020-12-10 20:13

@dmp1ce interesting, can you try running snap run --strace=--raw superproductivity and post the log to a pastebin? (the log may be too long for poasting in a comment here)

Edit: you need to pacman -S strace first

dmp1ce commented on 2020-12-10 20:01

@bboozzoo: Here is my output.

david@bar:~$ cat /proc/self/attr/current
david@bar:~$ SNAPD_DEBUG=1 SNAP_CONFINE_DEBUG=1 snap run superproductivity
2020/12/10 14:59:51.067755 tool_linux.go:68: DEBUG: re-exec not supported on distro "arch" yet
2020/12/10 14:59:51.082619 cmd_run.go:407: DEBUG: SELinux not enabled
DEBUG: umask reset, old umask was  022
DEBUG: security tag: snap.superproductivity.superproductivity
DEBUG: executable:   /usr/lib/snapd/snap-exec
DEBUG: confinement:  non-classic
DEBUG: base snap:    core18
DEBUG: ruid: 1000, euid: 0, suid: 0
DEBUG: rgid: 1000, egid: 1000, sgid: 1000
cannot query current apparmor profile: Invalid argument

bboozzoo commented on 2020-12-10 16:28

@dmp1ce what does cat /proc/self/attr/current show?

Can you upload the logs of SNAPD_DEBUG=1 SNAP_CONFINE_DEBUG=1 snap run superproductivity to some pastebin?

dmp1ce commented on 2020-12-10 16:03

@bboozzoo, I think something is wrong with snapd, because restarting apparmor didn't help me. I am using an LTS kernel.

Here is what I tried:

david@bar:~$ superproductivity 
cannot query current apparmor profile: Invalid argument
1 david@bar:~$ sudo systemctl restart apparmor
[sudo] password for david: 
david@bar:~$ superproductivity 
cannot query current apparmor profile: Invalid argument
1 david@bar:~$ uname -a
Linux bar 5.4.82-1-lts #1 SMP Tue, 08 Dec 2020 12:10:59 +0000 x86_64 GNU/Linux

bboozzoo commented on 2020-12-10 10:12

@dmp1ce hit this today after the kernel update, but restarting apparmor.service fixed it. Looks like aa_getcon() from libapparmor returned EINVAL, which is weird because it's supposed to go and read /proc/self/attr/current AFAIK.

dmp1ce commented on 2020-12-09 13:36

Is anyone here getting an apparmor error? I'm getting:

$ hello-world
cannot query current apparmor profile: Invalid argument

sbussetti commented on 2020-11-07 23:05

I've done a full system update as of 20201107.

Attempting to install the latest version of snapd from here (currently '2.47.1-2') fails for me in the following way:

$ git clone
$ cd snapd
$ makepkg -si

==> Making package: snapd 2.47.1-2 (Sat 07 Nov 2020 06:03:31 PM EST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found snapd-2.47.1.tar.xz
==> Validating source files with sha256sums...
    snapd-2.47.1.tar.xz ... Passed
==> Extracting sources...
  -> Extracting snapd-2.47.1.tar.xz with bsdtar
==> Starting prepare()...
==> Removing existing $pkgdir/ directory...
==> Starting build()...
*** Setting version to '2.47.1-2' from user.
panic: runtime error: slice bounds out of range [:3965974062] with capacity 566288

goroutine 1 [running]:
cmd/internal/goobj2.(*Reader).StringRef(0xc00063a7e0, 0x9f83, 0x38, 0x252)
        /usr/lib/go/src/cmd/internal/goobj2/objfile.go:561 +0x112
cmd/link/internal/loader.(*Loader).resolve(0xc00061c000, 0xc000620cc0, 0x38a7ffffffb, 0x40a4)
        /usr/lib/go/src/cmd/link/internal/loader/loader.go:603 +0xe5
cmd/link/internal/loader.Reloc2.Sym(0x7fcc5a07fbe8, 0xc000620cc0, 0xc00061c000, 0x0, 0x40a4)
        /usr/lib/go/src/cmd/link/internal/loader/loader.go:83 +0x48
        /usr/lib/go/src/cmd/link/internal/ld/deadcode.go:154 +0x1e9
        /usr/lib/go/src/cmd/link/internal/ld/deadcode.go:264 +0xcc
cmd/link/internal/ld.Main(0x86f840, 0x20, 0x20, 0x1, 0x7, 0x10, 0x0, 0x0, 0x6dab5f, 0x1b, ...)
        /usr/lib/go/src/cmd/link/internal/ld/main.go:235 +0xd3c
        /usr/lib/go/src/cmd/link/main.go:68 +0x1dc
==> ERROR: A failure occurred in build().

bboozzoo commented on 2020-10-26 17:08

@codyps applied, thank you!

codyps commented on 2020-10-26 16:53

Package currently fails to build for me with the error:

loadelf: $WORK/b060/_pkg_.a(_x011.o): 284706: sym#70: ignoring symbol in section 1 (type 0)
.rela: relocation target _cgo_26061493d47f_C2func_getaddrinfo not defined
/usr/lib/go/pkg/tool/linux_amd64/link: too many errors

This is fixed by adding -linkmode external to the go flags used. This is based on the current go packaging guidelines (

Here's a patch: