Package Details: snapd 2.75.2-1

Git Clone URL: https://aur.archlinux.org/snapd.git (read-only, click to copy)
Package Base: snapd
Description: Service and tools for management of snap packages.
Upstream URL: https://github.com/snapcore/snapd
Licenses: GPL3
Conflicts: snap-confine
Submitter: Barthalion
Maintainer: bboozzoo (zyga)
Last Packager: bboozzoo
Votes: 231
Popularity: 3.35
First Submitted: 2018-01-07 17:37 (UTC)
Last Updated: 2026-04-20 08:01 (UTC)

Pinned Comments

bboozzoo commented on 2018-10-25 11:56 (UTC) (edited on 2025-07-10 11:42 (UTC) by bboozzoo)

Package update notes

2.36

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 https://wiki.archlinux.org/index.php/AppArmor 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
2.62

Since 2.62 snapd generated additional files describing the sandbox. The snapd service needs to be restarted after the update for snaps to continue working (unless the system is rebooted after the update, in which case no additional steps are needed). To restart, run systemctl restart snapd.service

2.70

Snapd 2.70 drops setuid permissions on /usr/lib/snapd/snap-confine in favor of explicit file capabilities. After an upgrade to 2.70, the users are prompted to restart the apparmor.service otherwise attempts to run snaps will error with cannot set capabilities message.

Latest Comments

« First ‹ Previous 1 .. 16 17 18 19 20 21 22 23 24 25 26 .. 28 Next › Last »

Gonzalo2683 commented on 2019-07-12 14:35 (UTC) (edited on 2019-07-12 14:41 (UTC) by Gonzalo2683)

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 (UTC)

@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.

Gonzalo2683 commented on 2019-07-09 14:38 (UTC)

@bboozzoo The problem persist, i have the same error even if run the makepkg -s.

bboozzoo commented on 2019-06-07 15:11 (UTC)

@Gonzalo2683 you need to install the packages listed in makedepends manually, or use makepkg -s. AUR helpers will likely do that for you automatically.

Gonzalo2683 commented on 2019-06-07 14:34 (UTC)

I have the following problem trying to instal snap: 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 Package libseccomp was not found in the pkg-config search path. Perhaps you should add the directory containinglibseccomp.pc' to the PKG_CONFIG_PATH environment variable No package 'libseccomp' found pkg-config: exit status 1 ==> ERROR: Se produjo un fallo en build(). Cancelando...

I have tried installing the package like this: sudo pacman -S libseccomp And although the package is installed, the problem persists.

Some help?

now-im commented on 2019-03-08 14:58 (UTC) (edited on 2019-03-08 19:14 (UTC) by now-im)

I am facing the following problems. Kindly help.

sudo snap refresh                                                      
error: too early for operation, device not yet seeded or device model not acknowledged

sudo snap install bitwarden journey mailspring                                                                                 
error: cannot install "bitwarden", "journey", "mailspring": cannot refresh, install, or download:
       soft-expired device authorization needs refresh

Solution:

I tried all of the solution and finally solved it. First Install the package jq from arch repo. Then execute the following commands. This should solve the problem.

$ systemctl stop snapd
$ sudo cat /var/lib/snapd/state.json | \
    jq 'delpaths([["data", "auth", "device"]])' > state.json-new
$ sudo cp state.json-new /var/lib/snapd/state.json
$ sudo systemctl start snapd

bboozzoo commented on 2018-12-23 08:43 (UTC)

@C0rn3j squashfs driver is in the kernel already. I don't see why you'd need to use squashfuse on Arch unless you're on a custom kernel without squashfs, or upgraded the kernel but did not reboot (effectively anything that loads drivers on-demand will fail at this point), or running Arch in a container.

The first and the last case could use optdepends, but IMO a wiki note would be more useful (or both even).

The upgraded kernel case is unfortunately a lost cause, unless fuse was it was already loaded, squashfuse will fail too.

after running it twice because of irrelevant snapd bug

Can you describe the problem?

C0rn3j commented on 2018-12-23 02:38 (UTC)

I just setup a fresh privileged LXD container with Arch.

I then installed this package, but was getting a hard middle finger from snapd.

After installing squashfuse and fuse3, I could snap install something just fine(after running it twice because of irrelevant snapd bug). Those two packages (not 100% sure that squashfuse is needed) are not even in optdepends.

rvlobato commented on 2018-12-18 16:25 (UTC)

Indeed, @bboozzoo, you were right, thanks! Now everything works fine.

bboozzoo commented on 2018-12-18 07:37 (UTC)

@rvlobato libgo.so is used by gcc-go. My guess would be you've built snapd using gcc-go and then it was removed or replaced with go. If you still have the package file, you can extract the .BUILDINFO file and see what was installed at the time. The upstream test suite running on Arch builds snapd using go. I'd recommend you install go, rebuild the package and pacman -U the new one.

FWIW, snap-update-ns is built statically, but also requires CGO. Proper flags are passed, to make it work. Maybe the go frontend provided by gcc-go interprets/handles the flags differently.

« First ‹ Previous 1 .. 16 17 18 19 20 21 22 23 24 25 26 .. 28 Next › Last »