I was successfully able to install snapd using the repo https://download.opensuse.org/repositories/system:/snappy/openSUSE_Tumbleweed on my fresh Tumbleweed-Slowroll install but I cannot start the snapd.service. The version of snapd is 2.65.1-1.5 and OS info is:
NAME="openSUSE Tumbleweed-Slowroll"
# VERSION="20240901"
ID="opensuse-slowroll"
ID_LIKE="opensuse suse"
VERSION_ID="20240901"
PRETTY_NAME="openSUSE Tumbleweed-Slowroll"
ANSI_COLOR="0;32"
# CPE 2.3 format, boo#1217921
CPE_NAME="cpe:2.3:o:opensuse:slowroll:20240901:*:*:*:*:*:*:*"
#CPE 2.2 format
#CPE_NAME="cpe:/o:opensuse:slowroll:20240901"
BUG_REPORT_URL="https://bugzilla.opensuse.org"
SUPPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org"
DOCUMENTATION_URL="https://en.opensuse.org/openSUSE:Slowroll"
LOGO="distributor-logo-Slowroll"
With kernel version 6.10.8-1-default
Here’s the status results from systemd for the socket and the service. I noticed the last line, I do not have /usr/lib/snapd/snap-seccomp but I do have /usr/libexec/snapd/snap-seccomp.
× snapd.socket - Socket activation for snappy daemon
Loaded: loaded (/usr/lib/systemd/system/snapd.socket; disabled; preset: disabled)
Active: failed (Result: service-start-limit-hit) since Mon 2024-09-16 15:40:55 EDT; 27min ago
Duration: 1.166s
Invocation: 3d6cb82ece5246ffba824cfc45d188dc
Triggers: ● snapd.service
Listen: /run/snapd.socket (Stream)
/run/snapd-snap.socket (Stream)
CPU: 213us
Sep 16 15:40:54 computername systemd[1]: Starting Socket activation for snappy daemon...
Sep 16 15:40:54 computername systemd[1]: Listening on Socket activation for snappy daemon.
Sep 16 15:40:55 computername systemd[1]: snapd.socket: Failed with result 'service-start-limit-hit'.
computername:~ # systemctl status snapd.service
× snapd.service - Snap Daemon
Loaded: loaded (/usr/lib/systemd/system/snapd.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Mon 2024-09-16 15:40:55 EDT; 27min ago
Invocation: 0194b68199244846a6c20d1f11d0b4d2
TriggeredBy: × snapd.socket
Main PID: 29678 (code=exited, status=1/FAILURE)
Sep 16 15:40:55 computername snapd[29678]: daemon.go:353: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Sep 16 15:40:55 computername snapd[29678]: backends.go:58: AppArmor status: apparmor is enabled but some kernel features are missing: dbus, network
Sep 16 15:40:55 computername snapd[29678]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: fork/exec /usr/lib/snapd/snap-seccomp: no such file or directory]
Sep 16 15:40:55 computername systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
Sep 16 15:40:55 computername systemd[1]: snapd.service: Failed with result 'exit-code'.
Sep 16 15:40:55 computername systemd[1]: snapd.service: Scheduled restart job, restart counter is at 5.
Sep 16 15:40:55 computername systemd[1]: snapd.service: Start request repeated too quickly.
Sep 16 15:40:55 computername systemd[1]: snapd.service: Failed with result 'exit-code'.
Sep 16 15:40:55 computername systemd[1]: Failed to start Snap Daemon.
Sep 16 15:40:55 computername systemd[1]: snapd.service: Triggering OnFailure= dependencies.