Tumbleweed, error when trying to install a snap

user_name_forbidden · January 22, 2024, 1:28pm

I got an error when trying to install a snap. See below. Can this be fixed? I’m using Tumbleweed.

advait@localhost:~> snap version
snap                 2.61.1
snapd                2.61.1
series               16
opensuse-tumbleweed  20240119
kernel               6.6.11-1-default
WARNING: There is 1 new warning. See 'snap warnings'.
advait@localhost:~> snap warnings
last-occurrence:  5 days ago, at 20:35 IST
warning: |
  the snapd.apparmor service is disabled; snap applications will likely not start.
  Run "systemctl enable --now snapd.apparmor" to correct this.
advait@localhost:~> sudo systemctl enable --now snapd.apparmor
[sudo] password for root: 
advait@localhost:~> snap version
snap                 2.61.1
snapd                2.61.1
series               16
opensuse-tumbleweed  20240119
kernel               6.6.11-1-default
advait@localhost:~> sudo snap install syncthing-gael
error: system does not fully support snapd: cannot mount squashfs image using "squashfs":
       ----- mount: /tmp/syscheck-mountpoint-137096283: wrong fs type, bad option, bad superblock
       on /dev/loop0, missing codepage or helper program, or other error.

       dmesg(1) may have more information after failed mount system call.

       -----
advait@localhost:~>

mborzecki1 · January 22, 2024, 4:08pm

This is highly unexpected, I literally have a laptop on TW, using the same kernel but a snapshot from 18.01 and no issues with snaps. Can you attach the output of journalctl -u snapd --no-pager ?

user_name_forbidden · January 23, 2024, 8:17am

Sure, here it is below. An easier to read version is here: https://docs.google.com/document/d/1IWtzy5SwVsOztxLrGz2B-e19SW34qc5blVLH6flj1h4/edit?usp=sharing

advait@localhost:~> sudo journalctl -u snapd --no-pager
[sudo] password for root: 
Jan 17 20:35:42 localhost.localdomain systemd[1]: Starting Snap Daemon...
Jan 17 20:35:42 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 19444, but reception only permitted for main PID 19435
Jan 17 20:35:42 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 19450, but reception only permitted for main PID 19435
Jan 17 20:35:42 localhost.localdomain snapd[19435]: overlord.go:271: Acquiring state lock file
Jan 17 20:35:42 localhost.localdomain snapd[19435]: overlord.go:276: Acquired state lock file
Jan 17 20:35:42 localhost.localdomain snapd[19435]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240114 (amd64) linux/6.6.11-1-default.
Jan 17 20:35:42 localhost.localdomain snapd[19435]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 17 20:35:42 localhost.localdomain snapd[19435]: -----
Jan 17 20:35:42 localhost.localdomain snapd[19435]: mount: /tmp/syscheck-mountpoint-2917584480: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 17 20:35:42 localhost.localdomain snapd[19435]:        dmesg(1) may have more information after failed mount system call.
Jan 17 20:35:42 localhost.localdomain snapd[19435]: -----
Jan 17 20:35:42 localhost.localdomain snapd[19435]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 17 20:35:42 localhost.localdomain snapd[19435]: backends.go:58: AppArmor status: apparmor not enabled
Jan 17 20:35:42 localhost.localdomain snapd[19435]: helpers.go:146: error trying to compare the snap system key: system-key missing on disk
Jan 17 20:35:42 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 19514, but reception only permitted for main PID 19435
Jan 17 20:35:42 localhost.localdomain systemd[1]: Started Snap Daemon.
Jan 17 20:35:47 localhost.localdomain snapd[19435]: daemon.go:519: gracefully waiting for running hooks
Jan 17 20:35:47 localhost.localdomain snapd[19435]: daemon.go:521: done waiting for running hooks
Jan 17 20:35:50 localhost.localdomain snapd[19435]: overlord.go:515: Released state lock file
Jan 17 20:35:50 localhost.localdomain snapd[19435]: daemon stop requested to wait for socket activation
Jan 17 20:35:50 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
-- Boot c5afb0df201a49f7ada464f1b76b96a5 --
Jan 17 20:38:27 localhost systemd[1]: Starting Snap Daemon...
Jan 17 20:38:27 localhost snapd[1369]: overlord.go:271: Acquiring state lock file
Jan 17 20:38:27 localhost snapd[1369]: overlord.go:276: Acquired state lock file
Jan 17 20:38:27 localhost systemd[1]: snapd.service: Got notification message from PID 1511, but reception only permitted for main PID 1369
Jan 17 20:38:27 localhost systemd[1]: snapd.service: Got notification message from PID 1513, but reception only permitted for main PID 1369
Jan 17 20:38:27 localhost snapd[1369]: patch.go:64: Patching system state level 6 to sublevel 1...
Jan 17 20:38:27 localhost snapd[1369]: patch.go:64: Patching system state level 6 to sublevel 2...
Jan 17 20:38:27 localhost snapd[1369]: patch.go:64: Patching system state level 6 to sublevel 3...
Jan 17 20:38:27 localhost snapd[1369]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240114 (amd64) linux/6.6.11-1-default.
Jan 17 20:38:27 localhost snapd[1369]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 17 20:38:27 localhost snapd[1369]: -----
Jan 17 20:38:27 localhost snapd[1369]: mount: /tmp/syscheck-mountpoint-891625670: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 17 20:38:27 localhost snapd[1369]:        dmesg(1) may have more information after failed mount system call.
Jan 17 20:38:27 localhost snapd[1369]: -----
Jan 17 20:38:27 localhost snapd[1369]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 17 20:38:27 localhost snapd[1369]: backends.go:58: AppArmor status: apparmor not enabled
Jan 17 20:38:27 localhost systemd[1]: snapd.service: Got notification message from PID 1566, but reception only permitted for main PID 1369
Jan 17 20:38:27 localhost systemd[1]: Started Snap Daemon.
Jan 17 20:39:02 localhost.localdomain snapd[1369]: daemon.go:519: gracefully waiting for running hooks
Jan 17 20:39:02 localhost.localdomain snapd[1369]: daemon.go:521: done waiting for running hooks
Jan 17 20:39:05 localhost.localdomain snapd[1369]: overlord.go:515: Released state lock file
Jan 17 20:39:05 localhost.localdomain snapd[1369]: daemon stop requested to wait for socket activation
Jan 17 20:39:05 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
-- Boot 63f66a4f5796430f95e9319238c2061b --
Jan 18 06:47:48 localhost systemd[1]: Starting Snap Daemon...
Jan 18 06:47:49 localhost systemd[1]: snapd.service: Got notification message from PID 1483, but reception only permitted for main PID 1344
Jan 18 06:47:49 localhost systemd[1]: snapd.service: Got notification message from PID 1499, but reception only permitted for main PID 1344
Jan 18 06:47:49 localhost snapd[1344]: overlord.go:271: Acquiring state lock file
Jan 18 06:47:49 localhost snapd[1344]: overlord.go:276: Acquired state lock file
Jan 18 06:47:49 localhost snapd[1344]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240114 (amd64) linux/6.6.11-1-default.
Jan 18 06:47:49 localhost snapd[1344]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 18 06:47:49 localhost snapd[1344]: -----
Jan 18 06:47:49 localhost snapd[1344]: mount: /tmp/syscheck-mountpoint-3690487189: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 18 06:47:49 localhost snapd[1344]:        dmesg(1) may have more information after failed mount system call.
Jan 18 06:47:49 localhost snapd[1344]: -----
Jan 18 06:47:49 localhost snapd[1344]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 18 06:47:49 localhost snapd[1344]: backends.go:58: AppArmor status: apparmor not enabled
Jan 18 06:47:49 localhost systemd[1]: Started Snap Daemon.
Jan 18 06:47:54 localhost.localdomain snapd[1344]: daemon.go:519: gracefully waiting for running hooks
Jan 18 06:47:54 localhost.localdomain snapd[1344]: daemon.go:521: done waiting for running hooks
Jan 18 06:47:57 localhost.localdomain snapd[1344]: overlord.go:515: Released state lock file
Jan 18 06:47:57 localhost.localdomain snapd[1344]: daemon stop requested to wait for socket activation
Jan 18 06:47:57 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
-- Boot 077797f817c544018061429ec7438359 --
Jan 18 10:26:42 localhost systemd[1]: Starting Snap Daemon...
Jan 18 10:26:43 localhost systemd[1]: snapd.service: Got notification message from PID 1620, but reception only permitted for main PID 1363
Jan 18 10:26:43 localhost systemd[1]: snapd.service: Got notification message from PID 1624, but reception only permitted for main PID 1363
Jan 18 10:26:43 localhost snapd[1363]: overlord.go:271: Acquiring state lock file
Jan 18 10:26:43 localhost snapd[1363]: overlord.go:276: Acquired state lock file
Jan 18 10:26:43 localhost snapd[1363]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240114 (amd64) linux/6.6.11-1-default.
Jan 18 10:26:43 localhost snapd[1363]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 18 10:26:43 localhost snapd[1363]: -----
Jan 18 10:26:43 localhost snapd[1363]: mount: /tmp/syscheck-mountpoint-3315721021: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 18 10:26:43 localhost snapd[1363]:        dmesg(1) may have more information after failed mount system call.
Jan 18 10:26:43 localhost snapd[1363]: -----
Jan 18 10:26:43 localhost snapd[1363]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 18 10:26:43 localhost snapd[1363]: backends.go:58: AppArmor status: apparmor not enabled
Jan 18 10:26:43 localhost systemd[1]: Started Snap Daemon.
Jan 18 10:26:48 localhost.localdomain snapd[1363]: daemon.go:519: gracefully waiting for running hooks
Jan 18 10:26:48 localhost.localdomain snapd[1363]: daemon.go:521: done waiting for running hooks
Jan 18 10:26:51 localhost.localdomain snapd[1363]: overlord.go:515: Released state lock file
Jan 18 10:26:51 localhost.localdomain snapd[1363]: daemon stop requested to wait for socket activation
Jan 18 10:26:51 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
Jan 18 16:43:55 localhost.localdomain systemd[1]: Starting Snap Daemon...
Jan 18 16:43:55 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 25828, but reception only permitted for main PID 25822
Jan 18 16:43:55 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 25829, but reception only permitted for main PID 25822
Jan 18 16:43:55 localhost.localdomain snapd[25822]: overlord.go:271: Acquiring state lock file
Jan 18 16:43:55 localhost.localdomain snapd[25822]: overlord.go:276: Acquired state lock file
Jan 18 16:43:55 localhost.localdomain snapd[25822]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240114 (amd64) linux/6.6.11-1-default.
Jan 18 16:43:55 localhost.localdomain snapd[25822]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 18 16:43:55 localhost.localdomain snapd[25822]: -----
Jan 18 16:43:55 localhost.localdomain snapd[25822]: mount: /tmp/syscheck-mountpoint-861146093: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 18 16:43:55 localhost.localdomain snapd[25822]:        dmesg(1) may have more information after failed mount system call.
Jan 18 16:43:55 localhost.localdomain snapd[25822]: -----
Jan 18 16:43:55 localhost.localdomain snapd[25822]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 18 16:43:55 localhost.localdomain snapd[25822]: backends.go:58: AppArmor status: apparmor not enabled
Jan 18 16:43:55 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 25848, but reception only permitted for main PID 25822
Jan 18 16:43:55 localhost.localdomain systemd[1]: Started Snap Daemon.
Jan 18 16:44:00 localhost.localdomain snapd[25822]: daemon.go:519: gracefully waiting for running hooks
Jan 18 16:44:00 localhost.localdomain snapd[25822]: daemon.go:521: done waiting for running hooks
Jan 18 16:44:03 localhost.localdomain snapd[25822]: overlord.go:515: Released state lock file
Jan 18 16:44:03 localhost.localdomain snapd[25822]: daemon stop requested to wait for socket activation
Jan 18 16:44:03 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
-- Boot afd31b73b903446296c90009f6779244 --
Jan 19 06:41:14 localhost systemd[1]: Starting Snap Daemon...
Jan 19 06:41:15 localhost systemd[1]: snapd.service: Got notification message from PID 1585, but reception only permitted for main PID 1352
Jan 19 06:41:15 localhost systemd[1]: snapd.service: Got notification message from PID 1588, but reception only permitted for main PID 1352
Jan 19 06:41:15 localhost snapd[1352]: overlord.go:271: Acquiring state lock file
Jan 19 06:41:15 localhost snapd[1352]: overlord.go:276: Acquired state lock file
Jan 19 06:41:15 localhost snapd[1352]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240114 (amd64) linux/6.6.11-1-default.
Jan 19 06:41:15 localhost snapd[1352]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 19 06:41:15 localhost snapd[1352]: -----
Jan 19 06:41:15 localhost snapd[1352]: mount: /tmp/syscheck-mountpoint-2455464564: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 19 06:41:15 localhost snapd[1352]:        dmesg(1) may have more information after failed mount system call.
Jan 19 06:41:15 localhost snapd[1352]: -----
Jan 19 06:41:15 localhost snapd[1352]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 19 06:41:15 localhost snapd[1352]: backends.go:58: AppArmor status: apparmor not enabled
Jan 19 06:41:15 localhost systemd[1]: Started Snap Daemon.
Jan 19 06:41:30 localhost.localdomain snapd[1352]: daemon.go:519: gracefully waiting for running hooks
Jan 19 06:41:30 localhost.localdomain snapd[1352]: daemon.go:521: done waiting for running hooks
Jan 19 06:41:33 localhost.localdomain snapd[1352]: overlord.go:515: Released state lock file
Jan 19 06:41:33 localhost.localdomain snapd[1352]: daemon stop requested to wait for socket activation
Jan 19 06:41:33 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
-- Boot eaf41415593242c0a477268313c40321 --
Jan 19 11:43:46 localhost systemd[1]: Starting Snap Daemon...
Jan 19 11:43:47 localhost systemd[1]: snapd.service: Got notification message from PID 1499, but reception only permitted for main PID 1356
Jan 19 11:43:47 localhost snapd[1356]: overlord.go:271: Acquiring state lock file
Jan 19 11:43:47 localhost snapd[1356]: overlord.go:276: Acquired state lock file
Jan 19 11:43:47 localhost snapd[1356]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240114 (amd64) linux/6.6.11-1-default.
Jan 19 11:43:47 localhost snapd[1356]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 19 11:43:47 localhost snapd[1356]: -----
Jan 19 11:43:47 localhost snapd[1356]: mount: /tmp/syscheck-mountpoint-3274879378: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 19 11:43:47 localhost snapd[1356]:        dmesg(1) may have more information after failed mount system call.
Jan 19 11:43:47 localhost snapd[1356]: -----
Jan 19 11:43:47 localhost snapd[1356]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 19 11:43:47 localhost snapd[1356]: backends.go:58: AppArmor status: apparmor not enabled
Jan 19 11:43:47 localhost systemd[1]: snapd.service: Got notification message from PID 1545, but reception only permitted for main PID 1356
Jan 19 11:43:47 localhost systemd[1]: Started Snap Daemon.
Jan 19 11:43:52 localhost.localdomain snapd[1356]: daemon.go:519: gracefully waiting for running hooks
Jan 19 11:43:52 localhost.localdomain snapd[1356]: daemon.go:521: done waiting for running hooks
Jan 19 11:43:55 localhost.localdomain snapd[1356]: overlord.go:515: Released state lock file
Jan 19 11:43:55 localhost.localdomain snapd[1356]: daemon stop requested to wait for socket activation
Jan 19 11:43:55 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
-- Boot 09fa37ef6715466dab5888c7fe2460a9 --
Jan 20 06:48:48 localhost systemd[1]: Starting Snap Daemon...
Jan 20 06:48:49 localhost systemd[1]: snapd.service: Got notification message from PID 1579, but reception only permitted for main PID 1316
Jan 20 06:48:49 localhost systemd[1]: snapd.service: Got notification message from PID 1588, but reception only permitted for main PID 1316
Jan 20 06:48:49 localhost snapd[1316]: overlord.go:271: Acquiring state lock file
Jan 20 06:48:49 localhost snapd[1316]: overlord.go:276: Acquired state lock file
Jan 20 06:48:49 localhost snapd[1316]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240114 (amd64) linux/6.6.11-1-default.
Jan 20 06:48:49 localhost snapd[1316]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 20 06:48:49 localhost snapd[1316]: -----
Jan 20 06:48:49 localhost snapd[1316]: mount: /tmp/syscheck-mountpoint-1740273261: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 20 06:48:49 localhost snapd[1316]:        dmesg(1) may have more information after failed mount system call.
Jan 20 06:48:49 localhost snapd[1316]: -----
Jan 20 06:48:49 localhost snapd[1316]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 20 06:48:49 localhost snapd[1316]: backends.go:58: AppArmor status: apparmor not enabled
Jan 20 06:48:49 localhost systemd[1]: Started Snap Daemon.
Jan 20 06:48:54 localhost.localdomain snapd[1316]: daemon.go:519: gracefully waiting for running hooks
Jan 20 06:48:54 localhost.localdomain snapd[1316]: daemon.go:521: done waiting for running hooks
Jan 20 06:48:57 localhost.localdomain snapd[1316]: overlord.go:515: Released state lock file
Jan 20 06:48:57 localhost.localdomain snapd[1316]: daemon stop requested to wait for socket activation
Jan 20 06:48:57 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
-- Boot 07cd79ec010642e6ba97300dd97bc765 --
Jan 20 08:22:38 localhost systemd[1]: Starting Snap Daemon...
Jan 20 08:22:39 localhost systemd[1]: snapd.service: Got notification message from PID 1567, but reception only permitted for main PID 1349
Jan 20 08:22:39 localhost systemd[1]: snapd.service: Got notification message from PID 1572, but reception only permitted for main PID 1349
Jan 20 08:22:39 localhost snapd[1349]: overlord.go:271: Acquiring state lock file
Jan 20 08:22:39 localhost snapd[1349]: overlord.go:276: Acquired state lock file
Jan 20 08:22:39 localhost snapd[1349]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240114 (amd64) linux/6.6.11-1-default.
Jan 20 08:22:39 localhost snapd[1349]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 20 08:22:39 localhost snapd[1349]: -----
Jan 20 08:22:39 localhost snapd[1349]: mount: /tmp/syscheck-mountpoint-1594770547: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 20 08:22:39 localhost snapd[1349]:        dmesg(1) may have more information after failed mount system call.
Jan 20 08:22:39 localhost snapd[1349]: -----
Jan 20 08:22:39 localhost snapd[1349]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 20 08:22:39 localhost snapd[1349]: backends.go:58: AppArmor status: apparmor not enabled
Jan 20 08:22:39 localhost systemd[1]: Started Snap Daemon.
Jan 20 08:22:44 localhost.localdomain snapd[1349]: daemon.go:519: gracefully waiting for running hooks
Jan 20 08:22:44 localhost.localdomain snapd[1349]: daemon.go:521: done waiting for running hooks
Jan 20 08:22:47 localhost.localdomain snapd[1349]: overlord.go:515: Released state lock file
Jan 20 08:22:47 localhost.localdomain snapd[1349]: daemon stop requested to wait for socket activation
Jan 20 08:22:47 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
-- Boot ab16eebf13ef4a2d88cb9235c95de058 --
Jan 20 08:29:32 localhost systemd[1]: Starting Snap Daemon...
Jan 20 08:29:33 localhost systemd[1]: snapd.service: Got notification message from PID 1600, but reception only permitted for main PID 1363
Jan 20 08:29:33 localhost systemd[1]: snapd.service: Got notification message from PID 1605, but reception only permitted for main PID 1363
Jan 20 08:29:33 localhost snapd[1363]: overlord.go:271: Acquiring state lock file
Jan 20 08:29:33 localhost snapd[1363]: overlord.go:276: Acquired state lock file
Jan 20 08:29:33 localhost snapd[1363]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240114 (amd64) linux/6.6.11-1-default.
Jan 20 08:29:33 localhost snapd[1363]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 20 08:29:33 localhost snapd[1363]: -----
Jan 20 08:29:33 localhost snapd[1363]: mount: /tmp/syscheck-mountpoint-3021952711: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 20 08:29:33 localhost snapd[1363]:        dmesg(1) may have more information after failed mount system call.
Jan 20 08:29:33 localhost snapd[1363]: -----
Jan 20 08:29:33 localhost snapd[1363]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 20 08:29:33 localhost snapd[1363]: backends.go:58: AppArmor status: apparmor not enabled
Jan 20 08:29:33 localhost systemd[1]: snapd.service: Got notification message from PID 1634, but reception only permitted for main PID 1363
Jan 20 08:29:33 localhost systemd[1]: Started Snap Daemon.
Jan 20 08:29:38 localhost.localdomain snapd[1363]: daemon.go:519: gracefully waiting for running hooks
Jan 20 08:29:38 localhost.localdomain snapd[1363]: daemon.go:521: done waiting for running hooks
Jan 20 08:29:41 localhost.localdomain snapd[1363]: overlord.go:515: Released state lock file
Jan 20 08:29:41 localhost.localdomain snapd[1363]: daemon stop requested to wait for socket activation
Jan 20 08:29:41 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
-- Boot c475dff0d71f40989b4252fd326a4897 --
Jan 20 09:17:14 localhost systemd[1]: Starting Snap Daemon...
Jan 20 09:17:14 localhost systemd[1]: snapd.service: Got notification message from PID 1576, but reception only permitted for main PID 1360
Jan 20 09:17:14 localhost systemd[1]: snapd.service: Got notification message from PID 1583, but reception only permitted for main PID 1360
Jan 20 09:17:14 localhost snapd[1360]: overlord.go:271: Acquiring state lock file
Jan 20 09:17:14 localhost snapd[1360]: overlord.go:276: Acquired state lock file
Jan 20 09:17:14 localhost snapd[1360]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240114 (amd64) linux/6.6.11-1-default.
Jan 20 09:17:14 localhost snapd[1360]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 20 09:17:14 localhost snapd[1360]: -----
Jan 20 09:17:14 localhost snapd[1360]: mount: /tmp/syscheck-mountpoint-3919543190: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 20 09:17:14 localhost snapd[1360]:        dmesg(1) may have more information after failed mount system call.
Jan 20 09:17:14 localhost snapd[1360]: -----
Jan 20 09:17:14 localhost snapd[1360]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 20 09:17:14 localhost snapd[1360]: backends.go:58: AppArmor status: apparmor not enabled
Jan 20 09:17:15 localhost systemd[1]: snapd.service: Got notification message from PID 1638, but reception only permitted for main PID 1360
Jan 20 09:17:15 localhost systemd[1]: Started Snap Daemon.
Jan 20 09:17:20 localhost.localdomain snapd[1360]: daemon.go:519: gracefully waiting for running hooks
Jan 20 09:17:20 localhost.localdomain snapd[1360]: daemon.go:521: done waiting for running hooks
Jan 20 09:17:23 localhost.localdomain snapd[1360]: overlord.go:515: Released state lock file
Jan 20 09:17:23 localhost.localdomain snapd[1360]: daemon stop requested to wait for socket activation
Jan 20 09:17:23 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
-- Boot 6e85d6836cd8472c96d098d218b72486 --
Jan 20 09:27:26 localhost systemd[1]: Starting Snap Daemon...
Jan 20 09:27:27 localhost systemd[1]: snapd.service: Got notification message from PID 1578, but reception only permitted for main PID 1358
Jan 20 09:27:27 localhost systemd[1]: snapd.service: Got notification message from PID 1588, but reception only permitted for main PID 1358
Jan 20 09:27:27 localhost snapd[1358]: overlord.go:271: Acquiring state lock file
Jan 20 09:27:27 localhost snapd[1358]: overlord.go:276: Acquired state lock file
Jan 20 09:27:27 localhost snapd[1358]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240114 (amd64) linux/6.6.11-1-default.
Jan 20 09:27:27 localhost snapd[1358]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 20 09:27:27 localhost snapd[1358]: -----
Jan 20 09:27:27 localhost snapd[1358]: mount: /tmp/syscheck-mountpoint-2055351632: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 20 09:27:27 localhost snapd[1358]:        dmesg(1) may have more information after failed mount system call.
Jan 20 09:27:27 localhost snapd[1358]: -----
Jan 20 09:27:27 localhost snapd[1358]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 20 09:27:27 localhost snapd[1358]: backends.go:58: AppArmor status: apparmor not enabled
Jan 20 09:27:27 localhost systemd[1]: snapd.service: Got notification message from PID 1623, but reception only permitted for main PID 1358
Jan 20 09:27:27 localhost systemd[1]: Started Snap Daemon.
Jan 20 09:27:32 localhost.localdomain snapd[1358]: daemon.go:519: gracefully waiting for running hooks
Jan 20 09:27:32 localhost.localdomain snapd[1358]: daemon.go:521: done waiting for running hooks
Jan 20 09:27:35 localhost.localdomain snapd[1358]: overlord.go:515: Released state lock file
Jan 20 09:27:35 localhost.localdomain snapd[1358]: daemon stop requested to wait for socket activation
Jan 20 09:27:35 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
-- Boot 0af826f7ed654d38a5e02e25d9466044 --
Jan 20 10:37:55 localhost systemd[1]: Starting Snap Daemon...
Jan 20 10:37:56 localhost systemd[1]: snapd.service: Got notification message from PID 1488, but reception only permitted for main PID 1392
Jan 20 10:37:56 localhost snapd[1392]: overlord.go:271: Acquiring state lock file
Jan 20 10:37:56 localhost snapd[1392]: overlord.go:276: Acquired state lock file
Jan 20 10:37:56 localhost snapd[1392]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240114 (amd64) linux/6.6.11-1-default.
Jan 20 10:37:56 localhost snapd[1392]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 20 10:37:56 localhost snapd[1392]: -----
Jan 20 10:37:56 localhost snapd[1392]: mount: /tmp/syscheck-mountpoint-1648168133: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 20 10:37:56 localhost snapd[1392]:        dmesg(1) may have more information after failed mount system call.
Jan 20 10:37:56 localhost snapd[1392]: -----
Jan 20 10:37:56 localhost snapd[1392]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 20 10:37:56 localhost snapd[1392]: backends.go:58: AppArmor status: apparmor not enabled
Jan 20 10:37:56 localhost systemd[1]: snapd.service: Got notification message from PID 1538, but reception only permitted for main PID 1392
Jan 20 10:37:56 localhost systemd[1]: Started Snap Daemon.
Jan 20 10:38:11 localhost.localdomain snapd[1392]: daemon.go:519: gracefully waiting for running hooks
Jan 20 10:38:11 localhost.localdomain snapd[1392]: daemon.go:521: done waiting for running hooks
Jan 20 10:38:14 localhost.localdomain snapd[1392]: overlord.go:515: Released state lock file
Jan 20 10:38:14 localhost.localdomain snapd[1392]: daemon stop requested to wait for socket activation
Jan 20 10:38:14 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
-- Boot d2ca816d28f24efe84e3cbd63249b385 --
Jan 21 05:12:17 localhost systemd[1]: Starting Snap Daemon...
Jan 21 05:12:18 localhost systemd[1]: snapd.service: Got notification message from PID 1510, but reception only permitted for main PID 1355
Jan 21 05:12:18 localhost snapd[1355]: overlord.go:271: Acquiring state lock file
Jan 21 05:12:18 localhost snapd[1355]: overlord.go:276: Acquired state lock file
Jan 21 05:12:18 localhost snapd[1355]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240114 (amd64) linux/6.6.11-1-default.
Jan 21 05:12:18 localhost snapd[1355]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 21 05:12:18 localhost snapd[1355]: -----
Jan 21 05:12:18 localhost snapd[1355]: mount: /tmp/syscheck-mountpoint-4152057620: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 21 05:12:18 localhost snapd[1355]:        dmesg(1) may have more information after failed mount system call.
Jan 21 05:12:18 localhost snapd[1355]: -----
Jan 21 05:12:18 localhost snapd[1355]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 21 05:12:18 localhost snapd[1355]: backends.go:58: AppArmor status: apparmor not enabled
Jan 21 05:12:18 localhost systemd[1]: snapd.service: Got notification message from PID 1547, but reception only permitted for main PID 1355
Jan 21 05:12:18 localhost systemd[1]: Started Snap Daemon.
Jan 21 05:12:23 localhost.localdomain snapd[1355]: daemon.go:519: gracefully waiting for running hooks
Jan 21 05:12:23 localhost.localdomain snapd[1355]: daemon.go:521: done waiting for running hooks
Jan 21 05:12:26 localhost.localdomain snapd[1355]: overlord.go:515: Released state lock file
Jan 21 05:12:26 localhost.localdomain snapd[1355]: daemon stop requested to wait for socket activation
Jan 21 05:12:26 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
-- Boot f9e6c638b95b4d94ad7376b4c2bb328f --
Jan 21 12:57:51 localhost systemd[1]: Starting Snap Daemon...
Jan 21 12:57:52 localhost systemd[1]: snapd.service: Got notification message from PID 1526, but reception only permitted for main PID 1350
Jan 21 12:57:52 localhost systemd[1]: snapd.service: Got notification message from PID 1534, but reception only permitted for main PID 1350
Jan 21 12:57:52 localhost snapd[1350]: overlord.go:271: Acquiring state lock file
Jan 21 12:57:52 localhost snapd[1350]: overlord.go:276: Acquired state lock file
Jan 21 12:57:52 localhost snapd[1350]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240114 (amd64) linux/6.6.11-1-default.
Jan 21 12:57:52 localhost snapd[1350]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 21 12:57:52 localhost snapd[1350]: -----
Jan 21 12:57:52 localhost snapd[1350]: mount: /tmp/syscheck-mountpoint-3546569937: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 21 12:57:52 localhost snapd[1350]:        dmesg(1) may have more information after failed mount system call.
Jan 21 12:57:52 localhost snapd[1350]: -----
Jan 21 12:57:52 localhost snapd[1350]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 21 12:57:52 localhost snapd[1350]: backends.go:58: AppArmor status: apparmor not enabled
Jan 21 12:57:52 localhost systemd[1]: snapd.service: Got notification message from PID 1579, but reception only permitted for main PID 1350
Jan 21 12:57:52 localhost systemd[1]: Started Snap Daemon.
Jan 21 12:57:57 localhost.localdomain snapd[1350]: daemon.go:519: gracefully waiting for running hooks
Jan 21 12:57:57 localhost.localdomain snapd[1350]: daemon.go:521: done waiting for running hooks
Jan 21 12:58:00 localhost.localdomain snapd[1350]: overlord.go:515: Released state lock file
Jan 21 12:58:00 localhost.localdomain snapd[1350]: daemon stop requested to wait for socket activation
Jan 21 12:58:00 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
-- Boot cf2fd9e5970f4b1c9222dfd2a6106d65 --
Jan 21 19:14:52 localhost systemd[1]: Starting Snap Daemon...
Jan 21 19:14:52 localhost systemd[1]: snapd.service: Got notification message from PID 1644, but reception only permitted for main PID 1384
Jan 21 19:14:52 localhost systemd[1]: snapd.service: Got notification message from PID 1645, but reception only permitted for main PID 1384
Jan 21 19:14:52 localhost snapd[1384]: overlord.go:271: Acquiring state lock file
Jan 21 19:14:52 localhost snapd[1384]: overlord.go:276: Acquired state lock file
Jan 21 19:14:52 localhost snapd[1384]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240114 (amd64) linux/6.6.11-1-default.
Jan 21 19:14:52 localhost snapd[1384]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 21 19:14:52 localhost snapd[1384]: -----
Jan 21 19:14:52 localhost snapd[1384]: mount: /tmp/syscheck-mountpoint-1894251362: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 21 19:14:52 localhost snapd[1384]:        dmesg(1) may have more information after failed mount system call.
Jan 21 19:14:52 localhost snapd[1384]: -----
Jan 21 19:14:52 localhost snapd[1384]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 21 19:14:52 localhost snapd[1384]: backends.go:58: AppArmor status: apparmor not enabled
Jan 21 19:14:52 localhost systemd[1]: snapd.service: Got notification message from PID 1680, but reception only permitted for main PID 1384
Jan 21 19:14:52 localhost systemd[1]: Started Snap Daemon.
Jan 21 19:15:07 localhost.localdomain snapd[1384]: daemon.go:519: gracefully waiting for running hooks
Jan 21 19:15:07 localhost.localdomain snapd[1384]: daemon.go:521: done waiting for running hooks
Jan 21 19:15:10 localhost.localdomain snapd[1384]: overlord.go:515: Released state lock file
Jan 21 19:15:10 localhost.localdomain snapd[1384]: daemon stop requested to wait for socket activation
Jan 21 19:15:10 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
-- Boot 2ff47dd77e1549e1b549de5306e8555c --
Jan 21 19:17:21 localhost systemd[1]: Starting Snap Daemon...
Jan 21 19:17:21 localhost snapd[1448]: overlord.go:271: Acquiring state lock file
Jan 21 19:17:21 localhost snapd[1448]: overlord.go:276: Acquired state lock file
Jan 21 19:17:21 localhost snapd[1448]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240114 (amd64) linux/6.6.11-1-default.
Jan 21 19:17:22 localhost snapd[1448]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 21 19:17:22 localhost snapd[1448]: -----
Jan 21 19:17:22 localhost snapd[1448]: mount: /tmp/syscheck-mountpoint-2395444449: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 21 19:17:22 localhost snapd[1448]:        dmesg(1) may have more information after failed mount system call.
Jan 21 19:17:22 localhost snapd[1448]: -----
Jan 21 19:17:22 localhost snapd[1448]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 21 19:17:22 localhost snapd[1448]: backends.go:58: AppArmor status: apparmor not enabled
Jan 21 19:17:22 localhost systemd[1]: snapd.service: Got notification message from PID 1606, but reception only permitted for main PID 1448
Jan 21 19:17:22 localhost systemd[1]: Started Snap Daemon.
Jan 21 19:17:27 localhost.localdomain snapd[1448]: daemon.go:519: gracefully waiting for running hooks
Jan 21 19:17:27 localhost.localdomain snapd[1448]: daemon.go:521: done waiting for running hooks
Jan 21 19:17:30 localhost.localdomain snapd[1448]: overlord.go:515: Released state lock file
Jan 21 19:17:30 localhost.localdomain snapd[1448]: daemon stop requested to wait for socket activation
Jan 21 19:17:30 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
-- Boot fabd6cbee6944d9aab623674a5ea830c --
Jan 21 19:41:27 localhost systemd[1]: Starting Snap Daemon...
Jan 21 19:41:28 localhost systemd[1]: snapd.service: Got notification message from PID 1632, but reception only permitted for main PID 1358
Jan 21 19:41:28 localhost snapd[1358]: overlord.go:271: Acquiring state lock file
Jan 21 19:41:28 localhost snapd[1358]: overlord.go:276: Acquired state lock file
Jan 21 19:41:28 localhost snapd[1358]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240114 (amd64) linux/6.6.11-1-default.
Jan 21 19:41:28 localhost snapd[1358]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 21 19:41:28 localhost snapd[1358]: -----
Jan 21 19:41:28 localhost snapd[1358]: mount: /tmp/syscheck-mountpoint-4182725302: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 21 19:41:28 localhost snapd[1358]:        dmesg(1) may have more information after failed mount system call.
Jan 21 19:41:28 localhost snapd[1358]: -----
Jan 21 19:41:28 localhost snapd[1358]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 21 19:41:28 localhost snapd[1358]: backends.go:58: AppArmor status: apparmor not enabled
Jan 21 19:41:28 localhost systemd[1]: Started Snap Daemon.
Jan 21 19:41:33 localhost.localdomain snapd[1358]: daemon.go:519: gracefully waiting for running hooks
Jan 21 19:41:33 localhost.localdomain snapd[1358]: daemon.go:521: done waiting for running hooks
Jan 21 19:41:36 localhost.localdomain snapd[1358]: overlord.go:515: Released state lock file
Jan 21 19:41:36 localhost.localdomain snapd[1358]: daemon stop requested to wait for socket activation
Jan 21 19:41:36 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
-- Boot 235a803c77644b7998d9728c875df3f0 --
Jan 22 06:08:08 localhost systemd[1]: Starting Snap Daemon...
Jan 22 06:08:08 localhost systemd[1]: snapd.service: Got notification message from PID 1501, but reception only permitted for main PID 1386
Jan 22 06:08:09 localhost snapd[1386]: overlord.go:271: Acquiring state lock file
Jan 22 06:08:09 localhost snapd[1386]: overlord.go:276: Acquired state lock file
Jan 22 06:08:09 localhost snapd[1386]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240114 (amd64) linux/6.6.11-1-default.
Jan 22 06:08:09 localhost snapd[1386]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 22 06:08:09 localhost snapd[1386]: -----
Jan 22 06:08:09 localhost snapd[1386]: mount: /tmp/syscheck-mountpoint-3175593140: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 22 06:08:09 localhost snapd[1386]:        dmesg(1) may have more information after failed mount system call.
Jan 22 06:08:09 localhost snapd[1386]: -----
Jan 22 06:08:09 localhost snapd[1386]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 22 06:08:09 localhost snapd[1386]: backends.go:58: AppArmor status: apparmor not enabled
Jan 22 06:08:09 localhost systemd[1]: snapd.service: Got notification message from PID 1547, but reception only permitted for main PID 1386
Jan 22 06:08:09 localhost systemd[1]: Started Snap Daemon.
Jan 22 06:08:14 localhost.localdomain snapd[1386]: daemon.go:519: gracefully waiting for running hooks
Jan 22 06:08:14 localhost.localdomain snapd[1386]: daemon.go:521: done waiting for running hooks
Jan 22 06:08:17 localhost.localdomain snapd[1386]: overlord.go:515: Released state lock file
Jan 22 06:08:17 localhost.localdomain snapd[1386]: daemon stop requested to wait for socket activation
Jan 22 06:08:17 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
-- Boot a610b7b16e5143ed9e36510beb89a925 --
Jan 22 16:41:07 localhost systemd[1]: Starting Snap Daemon...
Jan 22 16:41:07 localhost systemd[1]: snapd.service: Got notification message from PID 1773, but reception only permitted for main PID 1614
Jan 22 16:41:07 localhost snapd[1614]: overlord.go:271: Acquiring state lock file
Jan 22 16:41:07 localhost snapd[1614]: overlord.go:276: Acquired state lock file
Jan 22 16:41:07 localhost snapd[1614]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240119 (amd64) linux/6.6.11-1-default.
Jan 22 16:41:07 localhost snapd[1614]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 22 16:41:07 localhost snapd[1614]: -----
Jan 22 16:41:07 localhost snapd[1614]: mount: /tmp/syscheck-mountpoint-797730943: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 22 16:41:07 localhost snapd[1614]:        dmesg(1) may have more information after failed mount system call.
Jan 22 16:41:07 localhost snapd[1614]: -----
Jan 22 16:41:07 localhost snapd[1614]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 22 16:41:07 localhost snapd[1614]: backends.go:58: AppArmor status: apparmor not enabled
Jan 22 16:41:07 localhost systemd[1]: snapd.service: Got notification message from PID 1822, but reception only permitted for main PID 1614
Jan 22 16:41:07 localhost systemd[1]: Started Snap Daemon.
Jan 22 16:41:12 localhost.localdomain snapd[1614]: daemon.go:519: gracefully waiting for running hooks
Jan 22 16:41:12 localhost.localdomain snapd[1614]: daemon.go:521: done waiting for running hooks
Jan 22 16:41:15 localhost.localdomain snapd[1614]: overlord.go:515: Released state lock file
Jan 22 16:41:15 localhost.localdomain snapd[1614]: daemon stop requested to wait for socket activation
Jan 22 16:41:15 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
Jan 22 18:29:08 localhost.localdomain systemd[1]: Starting Snap Daemon...
Jan 22 18:29:08 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 11993, but reception only permitted for main PID 11987
Jan 22 18:29:08 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 11994, but reception only permitted for main PID 11987
Jan 22 18:29:08 localhost.localdomain snapd[11987]: overlord.go:271: Acquiring state lock file
Jan 22 18:29:08 localhost.localdomain snapd[11987]: overlord.go:276: Acquired state lock file
Jan 22 18:29:08 localhost.localdomain snapd[11987]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240119 (amd64) linux/6.6.11-1-default.
Jan 22 18:29:08 localhost.localdomain snapd[11987]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 22 18:29:08 localhost.localdomain snapd[11987]: -----
Jan 22 18:29:08 localhost.localdomain snapd[11987]: mount: /tmp/syscheck-mountpoint-1856242716: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 22 18:29:08 localhost.localdomain snapd[11987]:        dmesg(1) may have more information after failed mount system call.
Jan 22 18:29:08 localhost.localdomain snapd[11987]: -----
Jan 22 18:29:08 localhost.localdomain snapd[11987]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 22 18:29:08 localhost.localdomain snapd[11987]: backends.go:58: AppArmor status: apparmor not enabled
Jan 22 18:29:08 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 12015, but reception only permitted for main PID 11987
Jan 22 18:29:08 localhost.localdomain systemd[1]: Started Snap Daemon.
Jan 22 18:29:13 localhost.localdomain snapd[11987]: daemon.go:519: gracefully waiting for running hooks
Jan 22 18:29:13 localhost.localdomain snapd[11987]: daemon.go:521: done waiting for running hooks
Jan 22 18:29:16 localhost.localdomain snapd[11987]: overlord.go:515: Released state lock file
Jan 22 18:29:16 localhost.localdomain snapd[11987]: daemon stop requested to wait for socket activation
Jan 22 18:29:16 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
Jan 22 18:29:26 localhost.localdomain systemd[1]: Starting Snap Daemon...
Jan 22 18:29:26 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 12121, but reception only permitted for main PID 12115
Jan 22 18:29:26 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 12122, but reception only permitted for main PID 12115
Jan 22 18:29:26 localhost.localdomain snapd[12115]: overlord.go:271: Acquiring state lock file
Jan 22 18:29:26 localhost.localdomain snapd[12115]: overlord.go:276: Acquired state lock file
Jan 22 18:29:26 localhost.localdomain snapd[12115]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240119 (amd64) linux/6.6.11-1-default.
Jan 22 18:29:26 localhost.localdomain snapd[12115]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 22 18:29:26 localhost.localdomain snapd[12115]: -----
Jan 22 18:29:26 localhost.localdomain snapd[12115]: mount: /tmp/syscheck-mountpoint-1296340704: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 22 18:29:26 localhost.localdomain snapd[12115]:        dmesg(1) may have more information after failed mount system call.
Jan 22 18:29:26 localhost.localdomain snapd[12115]: -----
Jan 22 18:29:26 localhost.localdomain snapd[12115]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 22 18:29:26 localhost.localdomain snapd[12115]: backends.go:58: AppArmor status: apparmor not enabled
Jan 22 18:29:26 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 12144, but reception only permitted for main PID 12115
Jan 22 18:29:26 localhost.localdomain systemd[1]: Started Snap Daemon.
Jan 22 18:29:31 localhost.localdomain snapd[12115]: daemon.go:519: gracefully waiting for running hooks
Jan 22 18:29:31 localhost.localdomain snapd[12115]: daemon.go:521: done waiting for running hooks
Jan 22 18:29:34 localhost.localdomain snapd[12115]: overlord.go:515: Released state lock file
Jan 22 18:29:34 localhost.localdomain snapd[12115]: daemon stop requested to wait for socket activation
Jan 22 18:29:34 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
Jan 22 18:32:05 localhost.localdomain systemd[1]: Starting Snap Daemon...
Jan 22 18:32:05 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 14837, but reception only permitted for main PID 14831
Jan 22 18:32:05 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 14843, but reception only permitted for main PID 14831
Jan 22 18:32:05 localhost.localdomain snapd[14831]: overlord.go:271: Acquiring state lock file
Jan 22 18:32:05 localhost.localdomain snapd[14831]: overlord.go:276: Acquired state lock file
Jan 22 18:32:05 localhost.localdomain snapd[14831]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240119 (amd64) linux/6.6.11-1-default.
Jan 22 18:32:05 localhost.localdomain snapd[14831]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 22 18:32:05 localhost.localdomain snapd[14831]: -----
Jan 22 18:32:05 localhost.localdomain snapd[14831]: mount: /tmp/syscheck-mountpoint-2296081091: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 22 18:32:05 localhost.localdomain snapd[14831]:        dmesg(1) may have more information after failed mount system call.
Jan 22 18:32:05 localhost.localdomain snapd[14831]: -----
Jan 22 18:32:05 localhost.localdomain snapd[14831]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 22 18:32:05 localhost.localdomain snapd[14831]: backends.go:58: AppArmor status: apparmor not enabled
Jan 22 18:32:05 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 14863, but reception only permitted for main PID 14831
Jan 22 18:32:05 localhost.localdomain systemd[1]: Started Snap Daemon.
Jan 22 18:32:10 localhost.localdomain snapd[14831]: daemon.go:519: gracefully waiting for running hooks
Jan 22 18:32:10 localhost.localdomain snapd[14831]: daemon.go:521: done waiting for running hooks
Jan 22 18:32:13 localhost.localdomain snapd[14831]: overlord.go:515: Released state lock file
Jan 22 18:32:13 localhost.localdomain snapd[14831]: daemon stop requested to wait for socket activation
Jan 22 18:32:13 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
Jan 22 18:34:04 localhost.localdomain systemd[1]: Starting Snap Daemon...
Jan 22 18:34:04 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 17248, but reception only permitted for main PID 17243
Jan 22 18:34:04 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 17255, but reception only permitted for main PID 17243
Jan 22 18:34:04 localhost.localdomain snapd[17243]: overlord.go:271: Acquiring state lock file
Jan 22 18:34:04 localhost.localdomain snapd[17243]: overlord.go:276: Acquired state lock file
Jan 22 18:34:04 localhost.localdomain snapd[17243]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240119 (amd64) linux/6.6.11-1-default.
Jan 22 18:34:04 localhost.localdomain snapd[17243]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 22 18:34:04 localhost.localdomain snapd[17243]: -----
Jan 22 18:34:04 localhost.localdomain snapd[17243]: mount: /tmp/syscheck-mountpoint-137096283: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 22 18:34:04 localhost.localdomain snapd[17243]:        dmesg(1) may have more information after failed mount system call.
Jan 22 18:34:04 localhost.localdomain snapd[17243]: -----
Jan 22 18:34:04 localhost.localdomain snapd[17243]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 22 18:34:04 localhost.localdomain snapd[17243]: backends.go:58: AppArmor status: apparmor not enabled
Jan 22 18:34:04 localhost.localdomain systemd[1]: snapd.service: Got notification message from PID 17270, but reception only permitted for main PID 17243
Jan 22 18:34:04 localhost.localdomain systemd[1]: Started Snap Daemon.
Jan 22 18:34:09 localhost.localdomain snapd[17243]: daemon.go:519: gracefully waiting for running hooks
Jan 22 18:34:09 localhost.localdomain snapd[17243]: daemon.go:521: done waiting for running hooks
Jan 22 18:34:12 localhost.localdomain snapd[17243]: overlord.go:515: Released state lock file
Jan 22 18:34:12 localhost.localdomain snapd[17243]: daemon stop requested to wait for socket activation
Jan 22 18:34:12 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
-- Boot 85ef9721868c4ca4ab443f3cb2d14617 --
Jan 23 06:20:44 localhost systemd[1]: Starting Snap Daemon...
Jan 23 06:20:44 localhost systemd[1]: snapd.service: Got notification message from PID 1504, but reception only permitted for main PID 1372
Jan 23 06:20:45 localhost snapd[1372]: overlord.go:271: Acquiring state lock file
Jan 23 06:20:45 localhost snapd[1372]: overlord.go:276: Acquired state lock file
Jan 23 06:20:45 localhost snapd[1372]: daemon.go:247: started snapd/2.61.1 (series 16; classic; devmode) opensuse-tumbleweed/20240119 (amd64) linux/6.6.11-1-default.
Jan 23 06:20:45 localhost snapd[1372]: main.go:125: system does not fully support snapd: cannot mount squashfs image using "squashfs":
Jan 23 06:20:45 localhost snapd[1372]: -----
Jan 23 06:20:45 localhost snapd[1372]: mount: /tmp/syscheck-mountpoint-2917984981: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Jan 23 06:20:45 localhost snapd[1372]:        dmesg(1) may have more information after failed mount system call.
Jan 23 06:20:45 localhost snapd[1372]: -----
Jan 23 06:20:45 localhost snapd[1372]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jan 23 06:20:45 localhost snapd[1372]: backends.go:58: AppArmor status: apparmor not enabled
Jan 23 06:20:45 localhost systemd[1]: Started Snap Daemon.
Jan 23 06:21:00 localhost.localdomain snapd[1372]: daemon.go:519: gracefully waiting for running hooks
Jan 23 06:21:00 localhost.localdomain snapd[1372]: daemon.go:521: done waiting for running hooks
Jan 23 06:21:03 localhost.localdomain snapd[1372]: overlord.go:515: Released state lock file
Jan 23 06:21:03 localhost.localdomain snapd[1372]: daemon stop requested to wait for socket activation
Jan 23 06:21:03 localhost.localdomain systemd[1]: snapd.service: Deactivated successfully.
advait@localhost:~>

mborzecki1 · January 23, 2024, 8:21am

Are there any denials which appear to be related? ausearch -m AVC should show then. I’m a bit confused why it’s showing that AppArmor isn’t enabled either. Are you using SELinux by any chance?

user_name_forbidden · January 23, 2024, 8:27am

Looks like yes…? See below.

advait@localhost:~> getenforce
Absolute path to 'getenforce' is '/usr/sbin/getenforce', so running it may require superuser privileges (eg. root).
advait@localhost:~> sudo getenforce
[sudo] password for root: 
Permissive
advait@localhost:~>

mborzecki1 · January 23, 2024, 8:33am

Right, that may explain the failure. I’m afraid the snapd package does not ship with SELinux policy files on openSUSE, and on that platform it’s primarily tested by the upstream with AppArmor.

I maintain a SELinux policy which is shipped with Fedora/EPEL packages, but it’s compatible with the variant of core policy shipped with those distros. I have no idea what it would take make the policy work with whatever variant of the core-policy shipped in openSUSE. Hopefully it’s close to the upstream.

In any way, I frankly don’t know what is the level of support of SELinux on openSUSE, and what can break in such a configuration.

user_name_forbidden · January 23, 2024, 10:05am

Here’s the output of this command: https://docs.google.com/document/d/1OoedH2lgS7PSlBssahl7IHlIKP3EIXNTdNbJ2II33Zs/edit?usp=sharing

It’s a big document.

user_name_forbidden · January 23, 2024, 10:09am

Have other Tumbleweed users had issues trying to run snapd? If yes, a lot of people? Or just a few?

user_name_forbidden · January 23, 2024, 10:10am

Could it be fixed on Tumbleweed by running snapd in some kind of container? Like Podman?

mborzecki1 · January 23, 2024, 10:11am

Not really, the host would have to support SELinux, or you’d need to have a kernel which supports LSM stacking, but that isn’t in the mainline yet AFAIU.

user_name_forbidden · January 23, 2024, 10:13am

Any helpful info here?

advait@localhost:~> snap list
No snaps are installed yet. Try 'snap install hello-world'.
advait@localhost:~> sudo snap install hello-world
[sudo] password for root: 
error: system does not fully support snapd: cannot mount squashfs image using "squashfs": -----
       mount: /tmp/syscheck-mountpoint-1529666139: wrong fs type, bad option, bad superblock on
       /dev/loop0, missing codepage or helper program, or other error.

       dmesg(1) may have more information after failed mount system call.

       -----
advait@localhost:~>

mborzecki1 · January 23, 2024, 10:15am

If it’s your machine then you can try the reverse of steps here: https://en.opensuse.org/SDB:SELinux if it’s a shared host, and your openSUSE is inside the container, then you’d need to talk to the host owner/administrator.

user_name_forbidden · January 23, 2024, 10:34am

This is just my own personal home laptop, which is not connected to any network. Right now SELinux is set to Permissive. Should I just try to uninstall SELinux? [[ sudo zypper remove selinux ]] Will uninstalling SELinux possibly cause other problems?

I’m just an average home computer user. I do some browsing, manage some docs and not much else. No server, no NAS, no RAID, no home network. Just some basic apps on my laptop.

mborzecki1 · January 23, 2024, 11:24am

Right, so I’d suggest to try the reverse of the steps outlined for Tumbleweed in the wiki. You can also try openSUSE forums, they’re usually a helpful bunch: https://forums.opensuse.org/

user_name_forbidden · January 23, 2024, 3:00pm

OK, I’ll follow up. Thanks.