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.22
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 .. 13 14 15 16 17 18 19 20 21 22 23 .. 28 Next › Last »

bboozzoo commented on 2020-04-24 06:28 (UTC)

@WomboCombo I suspect I should set GO111MODULE=off in the PKGBUILD. Surprisingly, this does not come up in either chroot or my regular shell. Just checked that we already set that in the test environments on Arch. Unfortunately snapd does not use modules yet because of quite old Go versions used on other distros.

WomboCombo commented on 2020-04-23 20:27 (UTC) (edited on 2020-04-24 05:15 (UTC) by WomboCombo)

Currerntly running into this error when installing snapd. Any ideas how to fix it?

==> Making package: snapd 2.44.3-1 (Thu 23 Apr 2020 10:16:45 PM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found snapd-2.44.3.tar.xz
==> Validating source files with sha256sums...
    snapd-2.44.3.tar.xz ... Passed
==> Extracting sources...
  -> Extracting snapd-2.44.3.tar.xz with bsdtar
==> Starting prepare()...
==> Removing existing $pkgdir/ directory...
==> Starting build()...
*** Setting version to '2.44.3-1' from user.
can't load package: cannot find module providing package                     github.com/snapcore/snapd/cmd/snap: working directory is not part of a module
==> ERROR: A failure occurred in build().
    Aborting...

EDIT: Okay got it working by manually initializing the modules in the snapd directory with: 

go mod init

and then

go mod tidy

it's probably also not wrong to just run

go mod vendor

on your own if you run into this problem. I suspect the problem occured because I already hat a golang environment installed on my machine.

frankbe commented on 2020-03-05 15:21 (UTC)

@bboozzoo: Good point. Interestingly, I had the package group installed, but was missing a few group members. I guess it's because my arch installation is old and the base-devel group changed over time. Anyway, thanks for clearification.

bboozzoo commented on 2020-03-04 14:05 (UTC)

@frankbe there's no need to specify automake or autoconf in makedepends, the base-devel group is expected to be already installed. Consult https://wiki.archlinux.org/index.php/PKGBUILD#makedepends for details.

frankbe commented on 2020-03-04 13:23 (UTC) (edited on 2020-03-04 13:24 (UTC) by frankbe)

During the installation, I got two errors:

/data/arch_builds/snapd/PKGBUILD: Zeile 88: autoreconf: Kommando nicht gefunden.

SOLUTION: Installing package "autoconf".

Can't exec "aclocal": Datei oder Verzeichnis nicht gefunden at /usr/share/autoconf/Autom4te/FileUtils.pm line 326.
autoreconf: failed to run aclocal: No such file or directory

SOLUTION: Installing package "automake".

So, I think you should add this two packages to the depends or makedepends list.

bboozzoo commented on 2019-12-06 12:08 (UTC)

@rsevero I don't know about Artix. Maybe try asking questions on https://forum.snapcraft.io

rsevero commented on 2019-12-06 11:21 (UTC)

@bboozzoo, first of all, sorry for the delay.

Yes you are right, this is Artix, not Arch.

Is this the log you wanted?

https://pastebin.com/eMjqNqyR

bboozzoo commented on 2019-12-04 10:41 (UTC)

@Fixed looks to me that mathpix-snipping-tool loads Gtk2, and that in turn tries to load the theme engines. From what I could try out (app requires you to have some random online account), the login screen pops up correctly. It's probably some electron thing to depend on Gtk2. The publisher of the snap is free to use the content snap that provides the relevant engines, snap info mathpix-snipping-tool lists support@mathpix.com as the contact address.

Fixed commented on 2019-12-03 21:02 (UTC) (edited on 2019-12-14 09:05 (UTC) by Fixed)

@bboozzoo:

support@mathpix.com is silent for more than a week.

« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 28 Next › Last »