[solved] Cannot install snap on opensuse tumbleweed

snapd
1

Hello,

I try to install snap on opensuse tumbleweed.

I’ve follow this guide https://snapcraft.io/docs/installing-snap-on-opensuse

Everything went well until this command: sudo systemctl enable --now snapd

I’ve the following answer: “job for snapd.service failed because the control process exited with error code. See “systemctl status snapd.service” and “journalctl -xeu snapd.service” for details.”

Here are the details from the command: 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 Sat 2024-02-10 20:17:56 CET; 2min 0s ago
TriggeredBy: × snapd.socket
    Process: 9805 ExecStart=/usr/lib/snapd/snapd (code=exited, status=1/FAILURE)
   Main PID: 9805 (code=exited, status=1/FAILURE)
        CPU: 72ms

févr. 10 20:17:56 localhost.localdomain systemd[1]: snapd.service: Scheduled restart job, restart counter is at 5.
févr. 10 20:17:56 localhost.localdomain systemd[1]: snapd.service: Start request repeated too quickly.
févr. 10 20:17:56 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'.
févr. 10 20:17:56 localhost.localdomain systemd[1]: Failed to start Snap Daemon.
févr. 10 20:17:56 localhost.localdomain systemd[1]: snapd.service: Triggering OnFailure= dependencies.

journalctl -xeu snapd.service

× snapd.service - Snap Daemon
     Loaded: loaded (/usr/lib/systemd/system/snapd.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Sat 2024-02-10 20:17:56 CET; 2min 0s ago
TriggeredBy: × snapd.socket
    Process: 9805 ExecStart=/usr/lib/snapd/snapd (code=exited, status=1/FAILURE)
   Main PID: 9805 (code=exited, status=1/FAILURE)
        CPU: 72ms

févr. 10 20:17:56 localhost.localdomain systemd[1]: snapd.service: Scheduled restart job, restart counter is at 5.
févr. 10 20:17:56 localhost.localdomain systemd[1]: snapd.service: Start request repeated too quickly.
févr. 10 20:17:56 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'.
févr. 10 20:17:56 localhost.localdomain systemd[1]: Failed to start Snap Daemon.
févr. 10 20:17:56 localhost.localdomain systemd[1]: snapd.service: Triggering OnFailure= dependencies.
localhost:/home/bastien # journalctl -xeu snapd.service
░░ L'unité (unit) snapd.service a commencé à démarrer.
févr. 10 20:17:56 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 9811, but reception only permitted for main PID 9805
févr. 10 20:17:56 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 9814, but reception only permitted for main PID 9805
févr. 10 20:17:56 localhost.localdomain snapd[9805]: overlord.go:271: Acquiring state lock file
févr. 10 20:17:56 localhost.localdomain snapd[9805]: overlord.go:276: Acquired state lock file
févr. 10 20:17:56 localhost.localdomain snapd[9805]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240208 (amd64) linux/6.7.4-1-default.
févr. 10 20:17:56 localhost.localdomain snapd[9805]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
févr. 10 20:17:56 localhost.localdomain snapd[9805]: backends.go:58: AppArmor status: apparmor is enabled but some kernel features are missing: dbus, network
févr. 10 20:17:56 localhost.localdomain snapd[9805]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: fork/exec /usr/libexec/snapd/snap-seccomp: no such file o>
févr. 10 20:17:56 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStart= process belonging to unit snapd.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
févr. 10 20:17:56 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit snapd.service has entered the 'failed' state with result 'exit-code'.
févr. 10 20:17:56 localhost.localdomain systemd[1]: Failed to start Snap Daemon.
░░ Subject: L'unité (unit) snapd.service a échoué
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ L'unité (unit) snapd.service a échoué, avec le résultat failed.
févr. 10 20:17:56 localhost.localdomain systemd[1]: snapd.service: Triggering OnFailure= dependencies.
févr. 10 20:17:56 localhost.localdomain systemd[1]: snapd.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ Le redémarrage automatique de l'unité (unit) snapd.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
févr. 10 20:17:56 localhost.localdomain systemd[1]: snapd.service: Start request repeated too quickly.
févr. 10 20:17:56 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit snapd.service has entered the 'failed' state with result 'exit-code'.
févr. 10 20:17:56 localhost.localdomain systemd[1]: Failed to start Snap Daemon.
░░ Subject: L'unité (unit) snapd.service a échoué
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ L'unité (unit) snapd.service a échoué, avec le résultat failed.
févr. 10 20:17:56 localhost.localdomain systemd[1]: snapd.service: Triggering OnFailure= dependencies.

Can you help me please ?

2

Does /usr/libexec/snapd/snap-seccomp exist in your system? It’s part of the snapd package you installed using zypper.

Edit: just for the record, when adding the repository, did you swap out 15.3 for Tumbleweed like it says in the instructions?

3

when adding the repository, did you swap out 15.3 for Tumbleweed like it says in the instructions?

No, I forgot that. Now it’s good. Sorry, for my mistake and thank you for your Answer.

3 Likes
4

Dear All, I am facing the same issue even after swaping out, not sure how do i resolve system-key issue, i can confirm that the system-key file is in /var/lib

AppArmor status: apparmor is enabled but some kernel features are missing: dbus, network
apparmor module is loaded.
62 profiles are loaded.
62 profiles are in enforce mode.
   /usr/bin/lessopen.sh
   /usr/lib/snapd/snap-confine
   /usr/lib/snapd/snap-confine//mount-namespace-capture-helper
   /usr/libexec/snapd/snap-confine
   /usr/libexec/snapd/snap-confine//mount-namespace-capture-helper
   apache2
   apache2//DEFAULT_URI
   apache2//HANDLING_UNTRUSTED_INPUT
   apache2//phpsysinfo
   avahi-daemon
   dnsmasq
   dnsmasq//libvirt_leaseshelper
   dovecot
   dovecot-anvil
   dovecot-auth
   dovecot-config
   dovecot-deliver
   dovecot-dict
   dovecot-director
   dovecot-doveadm-server
   dovecot-dovecot-auth
   dovecot-dovecot-lda
   dovecot-dovecot-lda//sendmail
   dovecot-imap
   dovecot-imap-login
   dovecot-lmtp
   dovecot-log
   dovecot-managesieve
   dovecot-managesieve-login
   dovecot-pop3
   dovecot-pop3-login
   dovecot-replicator
   dovecot-script-login
   dovecot-ssl-params
   dovecot-stats
   identd
   klogd
   lsb_release
   mdnsd
   nmbd
   nscd
   ntpd
   nvidia_modprobe
   nvidia_modprobe//kmod
   php-fpm
   ping
   samba-bgqd
   samba-dcerpcd
   samba-rpcd
   samba-rpcd-classic
   samba-rpcd-spoolss
   smbd
   smbldap-useradd
   smbldap-useradd///etc/init.d/nscd
   syslog-ng
   syslogd
   traceroute
   unix-chkpwd
   winbindd
   zgrep
   zgrep//helper
   zgrep//sed
0 profiles are in complain mode.
0 profiles are in kill mode.
0 profiles are in unconfined mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
0 processes are in mixed mode.
0 processes are in kill mode.
5

backends.go:58: AppArmor status: apparmor is enabled but some kernel features are missing: dbus, networkcannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: fork/exec /usr/lib/snapd/snap-seccomp: no such file or directory]

6

Which openSUSE variant are you using, Leap, TW, Slowroll? Are you sure you have added the right repository?

7

Thank s , Yes its Leap-15.6

(https://download.opensuse.org/repositories/system:/snappy/openSUSE_Leap_15.6/x86_64) snappy
(https://download.opensuse.org/repositories/system:/snappy/openSUSE_Leap_15.6 snappy
8

Can you paste the contents of /etc/os-release?

9

here it is

NAME="openSUSE Leap"
VERSION="15.6"
ID="opensuse-leap"
ID_LIKE="suse opensuse"
VERSION_ID="15.6"
PRETTY_NAME="openSUSE Leap 15.6"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:15.6"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Leap"
LOGO="distributor-logo-Leap"
10

It worked, silly me , did reboot & worked,