This package doesn't play nice with lto enabled. Can you please add options=(!lto)?
Search Criteria
Package Details: snapd 2.75.2-1
Package Actions
| 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.42 |
| First Submitted: | 2018-01-07 17:37 (UTC) |
| Last Updated: | 2026-04-20 08:01 (UTC) |
Dependencies (18)
- apparmor (apparmor-gitAUR)
- libcap
- libseccomp (libseccomp-gitAUR)
- libsystemd (systemd-libs-gitAUR, systemd-libs-selinuxAUR, unshitted-systemd-libsAUR, systemd-liberated-libs-gitAUR, systemd-libs)
- squashfs-tools (squashfs-tools-gitAUR)
- apparmor (apparmor-gitAUR) (make)
- autoconf-archive (autoconf-archive-gitAUR) (make)
- git (git-gitAUR, git-glAUR, git-wd40AUR) (make)
- go (go-gitAUR, gcc-go-gitAUR, go-binAUR, goup-rsAUR, gcc-go-snapshotAUR, gcc-go) (make)
- go-tools (go-tools-gitAUR) (make)
- libcap (make)
- libseccomp (libseccomp-gitAUR) (make)
- m4 (m4-gitAUR) (make)
- python-docutils (make)
- systemd (systemd-gitAUR, systemd-selinuxAUR, unshitted-systemdAUR, systemd-liberated-gitAUR) (make)
- xfsprogs (xfsprogs-gitAUR) (make)
- bash-completion (bash-completion-gitAUR) (optional) – bash completion support
- xdg-desktop-portal (xdg-desktop-portal-gitAUR, xdg-desktop-portal-minimal-gitAUR) (optional) – desktop integration
Required by (17)
- aerofetch (optional)
- apmpkg (optional)
- arch-update-full (optional)
- arch-update-vai (optional)
- bauh (optional)
- bauh-staging (optional)
- bigfive-updater (optional)
- discover-snap
- khazaur (optional)
- libpamac-full
- lintd-bin (optional)
- meta-package-manager (optional)
- meta-package-manager-git (optional)
- pacup-arch-git (optional)
- paxs
- pman (optional)
- sysfetch (optional)
Sources (1)
Latest Comments
« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 28 Next › Last »
patlefort commented on 2022-06-15 13:44 (UTC)
illuser commented on 2022-05-10 13:01 (UTC)
Upstream has just merged fixes for when Clang is the C-compiler that is used by the system. It should resolve problems with building this package.
fabrixx commented on 2022-03-07 20:00 (UTC)
I get the error only if I update snapd with pamac. If I use yay everything works fine and the update takes effect.
I cannot update snapd via pamac.
bboozzoo commented on 2022-03-07 06:55 (UTC)
@gavmanz please see: https://wiki.archlinux.org/title/Arch_User_Repository#Getting_started and https://wiki.archlinux.org/title/PKGBUILD#makedepends I didn't make those guidelines, but I seriously doubt they make sense since the same problems pops up over and over again.
gavmanz commented on 2022-03-07 02:22 (UTC)
It seems that this depends on the "automake" package from the official repos, but it is not listed as a dependency. I had an install error about aclocal until installing automake.
bboozzoo commented on 2022-03-04 17:32 (UTC)
@bob-xygene hi, idk what pamac is. I assume it's some package builder? The snapd package builds fine with makepkg (and yay for that matter). I suggest you contact with pamac upstream, and collect a backtrace for them.
bob-xygene commented on 2022-03-04 17:22 (UTC)
snapd makes pamac-manager crash every new update, have to exclude snapd for pamac not crash. /strace -t pamac-manager .... 18:08:45 statx(AT_FDCWD, "/tmp/pamac/aur-franck/snapd-2.54.4-1", AT_STATX_SYNC_AS_STAT|AT_SYMLINK_NOFOLLOW|AT_NO_AUTOMOUNT, STATX_ALL, {stx_mask=STATX_BASIC_STATS|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFDIR|0755, stx_size=120, ...}) = 0 18:08:45 statx(AT_FDCWD, "/tmp/pamac/aur-franck/snapd-2.54.4-1/desc", AT_STATX_SYNC_AS_STAT|AT_SYMLINK_NOFOLLOW|AT_NO_AUTOMOUNT, STATX_ALL, {stx_mask=STATX_BASIC_STATS|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0644, stx_size=73, ...}) = 0 18:08:45 futex(0x55ae6f8f36c0, FUTEX_WAKE_PRIVATE, 1) = 1 18:08:45 futex(0x55ae6f8f36b0, FUTEX_WAKE_PRIVATE, 1) = 1 18:08:45 poll([{fd=4, events=POLLIN}, {fd=16, events=POLLIN}, {fd=20, events=POLLIN}], 3, 0) = 0 (Timeout) 18:08:45 poll([{fd=4, events=POLLIN}, {fd=16, events=POLLIN}, {fd=20, events=POLLIN}], 3, 0) = 1 ([{fd=4, revents=POLLIN}]) 18:08:45 read(4, "\1\0\0\0\0\0\0\0", 16) = 8 18:08:45 write(26, "%FILENAME%\nsnapd-2.54.4-1-any.pk"..., 39) = 39 18:08:45 write(26, "%NAME%\nsnapd\n\n", 14) = 14 18:08:45 write(26, "%VERSION%\n2.54.4-1\n\n", 20) = 20 18:08:45 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x55ab2a259c71} --- 18:08:45 +++ killed by SIGSEGV (core dumped) +++ Erreur de segmentation (core dumped)
Since its only snapd that does the crash it must be snapd the culprit. It crashes when writing this file : /tmp/pamac/aur-franck/snapd-2.54.4-1/desc
/cat /tmp/pamac/aur-franck/snapd-2.54.4-1/desc %FILENAME% snapd-2.54.4-1-any.pkg.tar
%NAME% snapd
%VERSION% 2.54.4-1
/pamac-manager --version Pamac 10.3.0-2
Is there any hope ?
nerveous commented on 2022-02-07 14:19 (UTC)
@bboozzoo still issue for me, so i decide to follow this tutorial https://snapcraft.io/docs/installing-snap-on-arch-linux
bboozzoo commented on 2022-02-07 06:23 (UTC)
@nerveous IDK, have you tried again? maybe github returned something silly. Is snapd-2.54.2.tar.xz even a valid tar archive? Do you have a proxy on your network?
==> Making package: snapd 2.54.2-1 (pon, 7 lut 2022, 07:22:00)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading snapd-2.54.2.tar.xz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 663 100 663 0 0 2426 0 --:--:-- --:--:-- --:--:-- 2428
100 4711k 100 4711k 0 0 5467k 0 --:--:-- --:--:-- --:--:-- 25.3M
-> Found 0001-Treat-XDG_DATA_DIRS-like-PATH.patch
==> Validating source files with sha256sums...
snapd-2.54.2.tar.xz ... Passed
0001-Treat-XDG_DATA_DIRS-like-PATH.patch ... Passed
==> Extracting sources...
nerveous commented on 2022-02-07 03:49 (UTC) (edited on 2022-02-07 03:50 (UTC) by nerveous)
What is this issue ?
==> Making package: snapd 2.54.2-1 (Mon Feb 7 10:48:37 2022)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found snapd-2.54.2.tar.xz
-> Found 0001-Treat-XDG_DATA_DIRS-like-PATH.patch
==> Validating source files with sha256sums...
snapd-2.54.2.tar.xz ... FAILED
0001-Treat-XDG_DATA_DIRS-like-PATH.patch ... Passed
==> ERROR: One or more files did not pass the validity check!
-> error making: snapd
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:
systemctl restart apparmor.servicesnapd:systemctl restart snapd.servicesystemctl enable --now snapd.apparmor.service2.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.service2.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.serviceotherwise attempts to run snaps will error withcannot set capabilitiesmessage.