@JayGatsby what do you mean by snaps no longer opening? Are snaps no longer being mounted?
Can you report this on https://forum.snapcraft.io/ and upload journalctl and SNAP_DEBUG=1 SNAP_CONFINE_DEBUG=1 snap run hello-world
logs?
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, mardy) |
Last Packager: | bboozzoo |
Votes: | 222 |
Popularity: | 3.99 |
First Submitted: | 2018-01-07 17:37 (UTC) |
Last Updated: | 2025-01-24 11:51 (UTC) |
« First ‹ Previous 1 .. 16 17 18 19 20 21 22 23 24 25 Next › Last »
@JayGatsby what do you mean by snaps no longer opening? Are snaps no longer being mounted?
Can you report this on https://forum.snapcraft.io/ and upload journalctl and SNAP_DEBUG=1 SNAP_CONFINE_DEBUG=1 snap run hello-world
logs?
snaps no longer opening for me - Wonding if this is something others are experiencing or isolated to my machine.
@rplanchuelo, autoconf is part of the base-devel group. Packages in base-devel are assumed to be installed when building (AUR) packages, and should not be included as build dependencies.
https://wiki.archlinux.org/index.php/Arch_User_Repository#Prerequisites
I have problems with the last update:
/home/rober/.cache/aurman/snapd/PKGBUILD: línea 74: autoreconf: no se encontró la orden ==> ERROR: Se produjo un fallo en build(). Cancelando... 2018-06-23 07:19:24,818 - wrappers - makepkg - ERROR - makepkg query makepkg -cf --noconfirm failed
I'VE JUST FOUND THE SOLUTION: You have to install "autoconf" in orther to execute "autoreconf" (line 74). Maybe autoconf should be a dependencia.
@ibrokemypie your current LDFLAGS
setting appears to be incorrect. ld
will be called like this: /usr/bin/ld .. -01 --sort-common --as-needed -z relro now
, notice that now
is passed without a preceding -z
, making ld
interpret it as an object file.
Can you edit your LDFLAGS
to be: LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now"
and build again?
@bboozzoo My makepkg.conf is here: https://hastebin.com/bozoduwete.coffeescript
@bboozzoo that's it! Thanks a lot for the quick response and fix for my problem. Cheers
@joopdo pushed a change to use the source tarball with vendor dependencies bundled in. Can you check if it works for you now?
Pinned Comments
bboozzoo commented on 2018-10-25 11:56 (UTC) (edited on 2024-04-09 07:39 (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.service
snapd
:systemctl restart snapd.service
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