Package Details: snapd 2.42-2

Git Clone URL: (read-only)
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: 98
Popularity: 5.120105
First Submitted: 2018-01-07 17:37
Last Updated: 2019-10-05 13:38

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

1 2 3 4 5 6 ... Next › Last »

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.

dharrigan commented on 2019-10-05 07:55


Getting build errors when attempting to install snapd (or snapd-git). Here's the output:

==> Validating source files with sha256sums...
    snapd-2.42.tar.xz ... Passed
==> Cleaning up...
==> Making package: snapd 2.42-1 (Sat 05 Oct 2019 08:51:16 BST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found snapd-2.42.tar.xz
==> Validating source files with sha256sums...
    snapd-2.42.tar.xz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting snapd-2.42.tar.xz with bsdtar
==> Starting prepare()...
==> Sources are ready.
==> Making package: snapd 2.42-1 (Sat 05 Oct 2019 08:51:17 BST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting build()...
*** Setting version to '2.42-1' from user.
go: finding latest
can't load package: package no matching versions for query "latest"
==> ERROR: A failure occurred in build().
Error making: snapd

homelessuser commented on 2019-10-02 03:22

@bboozzoo remmina was the application that had no fonts, but also snap store was missing fonts also.

bboozzoo commented on 2019-10-01 14:24

@homelessuser which snap had the fonts rendered incorrectly in your case?

bboozzoo commented on 2019-10-01 12:06

@homelessuser thanks for letting me know. Indeed, I can see the problem here too:

homelessuser commented on 2019-10-01 12:00

Fonts missing and replaced with empty boxes in 2.14.r1137. It looks exactly like this Host fonts not being read correctly?

bboozzoo commented on 2019-07-12 14:41

@Gonzalo2683 I think there's something broken in your system.

$ pkg-config --path libseccomp

Maybe try reinstalling libseccomp or using a clean chroot to build the package like described here:

Gonzalo2683 commented on 2019-07-12 14:35

Hello @bboozzoo the results was:

 gonza@Arch-Linux/ pacman -Q libseccomp 
libseccomp 2.4.1-2
 gonza@Arch-Linux/ pkg-config --cflags --libs libseccomp
Package libseccomp was not found in the pkg-config search path.
Perhaps you should add the directory containing `libseccomp.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libseccomp' found
 gonza@Arch-Linux/  
I can not find the location of the file 'libseccomp.pc' How would the correct way to create the environment variable called PKG_CONFIG_PATH?

bboozzoo commented on 2019-07-12 12:30

@Gonzalo2683 not sure I understand what's happening in your system then.

The libseccomp package is listed in makedepends, so it should get automatically installed when you run makepkg -s.

Can you verify that libseccomp is indeed installed? Try running pacman -Q libseccomp. If that works try pkg-config --cflags --libs libseccomp.