Help for snap-exec: cannot exec "/snap/chromium/2675/snap/command-chain/desktop-launch": no such file or directory

I am using an Arm device on Kylin OS(something like ubuntu 20.04)

I sudo snap install chromium, it works fine, but when i reboot, it goes:

wangyonggang@wangyonggang-pc:~$ snap run chromium
cannot snap-exec: cannot exec "/snap/chromium/2675/snap/command-chain/desktop-launch": no such file or directory

reinstall will work, until next reboot.

the snap-store also have the save problem:

wangyonggang@wangyonggang-pc:~$ snap-store
cannot snap-exec: cannot exec "/snap/snap-store/963/snap/command-chain/desktop-launch": no such file or directory

I tried sudo, same error.

here is more detail maybe useful:

-rwxr-xr-x 1 root root 149 10月 28 09:58 /snap/chromium/2675/snap/command-chain/desktop-launch
wangyonggang@wangyonggang-pc:~$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0         7:0    0     4K  1 loop /snap/bare/5
loop1         7:1    0  68.5M  1 loop /snap/core22/867
loop2         7:2    0 475.1M  1 loop /snap/gnome-42-2204/143
loop3         7:3    0  91.7M  1 loop /snap/gtk-common-themes/1535
loop4         7:4    0  64.8M  1 loop /snap/cups/981
loop5         7:5    0 156.8M  1 loop /snap/chromium/2675
loop6         7:6    0  11.8M  1 loop /snap/snap-store/963
loop7         7:7    0  35.5M  1 loop /snap/snapd/20298
loop8         7:8    0 276.8M  0 loop /opt/exagear/images/kylin
nvme0n1     259:0    0   477G  0 disk 
├─nvme0n1p1 259:1    0   512M  0 part /boot/efi
├─nvme0n1p2 259:2    0     2G  0 part /boot
├─nvme0n1p3 259:3    0   100G  0 part /
├─nvme0n1p4 259:4    0    53G  0 part 
├─nvme0n1p5 259:5    0 302.8G  0 part /data
└─nvme0n1p6 259:6    0  18.7G  0 part [SWAP]
wangyonggang@wangyonggang-pc:~$ sudo snap run --debug-log chromium
2023/11/02 10:11:42.207492 logger.go:92: DEBUG: enabled debug logging of early snap startup
2023/11/02 10:11:42.208982 logger.go:92: DEBUG: executing snap-confine from /snap/snapd/20298/usr/lib/snapd/snap-confine
2023/11/02 10:11:42.210654 logger.go:92: DEBUG: SELinux not enabled
2023/11/02 10:11:42.211569 logger.go:92: DEBUG: creating transient scope snap.chromium.chromium
2023/11/02 10:11:42.211623 logger.go:92: DEBUG: session bus is not available: cannot find session bus
2023/11/02 10:11:42.211640 logger.go:92: DEBUG: falling back to system bus
2023/11/02 10:11:42.213951 logger.go:92: DEBUG: using system bus now, session bus was not available
2023/11/02 10:11:42.217195 logger.go:92: DEBUG: create transient scope job: /org/freedesktop/systemd1/job/12277
2023/11/02 10:11:42.218564 logger.go:92: DEBUG: waited 4.490304ms for tracking
2023/11/02 10:11:42.218599 logger.go:92: DEBUG: -- snap startup {"stage":"snap to snap-confine", "time":"1698891102.218593"}
DEBUG: -- snap startup {"stage":"snap-confine enter", "time":"1698891102.221624"}
DEBUG: umask reset, old umask was  022
DEBUG: security tag: snap.chromium.chromium
DEBUG: executable:   /usr/lib/snapd/snap-exec
DEBUG: confinement:  non-classic
DEBUG: base snap:    core22
DEBUG: ruid: 0, euid: 0, suid: 0
DEBUG: rgid: 0, egid: 0, sgid: 0
DEBUG: apparmor is available on the system but has been disabled at boot
DEBUG: -- snap startup {"stage":"snap-confine mount namespace start", "time":"1698891102.222536"}
DEBUG: creating lock directory /run/snapd/lock (if missing)
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: opening lock directory /run/snapd/lock
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: opening lock file: /run/snapd/lock/.lock
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: sanity timeout initialized and set for 30 seconds
DEBUG: acquiring exclusive lock (scope (global), uid 0)
DEBUG: sanity timeout reset and disabled
DEBUG: ensuring that snap mount directory is shared
DEBUG: unsharing snap namespace directory
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: releasing lock 5
DEBUG: opened snap-update-ns executable as file descriptor 5
DEBUG: opened snap-discard-ns executable as file descriptor 6
DEBUG: creating lock directory /run/snapd/lock (if missing)
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: opening lock directory /run/snapd/lock
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: opening lock file: /run/snapd/lock/chromium.lock
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: sanity timeout initialized and set for 30 seconds
DEBUG: acquiring exclusive lock (scope chromium, uid 0)
DEBUG: sanity timeout reset and disabled
DEBUG: initializing mount namespace: chromium
DEBUG: setting up device cgroup
DEBUG: cannot find current tags symbol: /lib/aarch64-linux-gnu/libudev.so.1: undefined symbol: udev_device_has_current_tag
DEBUG: no current tags support present
DEBUG: inspecting type of device: /dev/dri/card1
DEBUG: inspecting type of device: /dev/dri/renderD128
DEBUG: inspecting type of device: /dev/dri/card0
DEBUG: cannot get major/minor numbers for syspath /sys/devices/pci0000:00/0000:00:00.0/0000:01:00.0/0000:02:01.0/0000:03:00.2/drm/card0/card0-DP-1
DEBUG: cannot get major/minor numbers for syspath /sys/devices/pci0000:00/0000:00:00.0/0000:01:00.0/0000:02:01.0/0000:03:00.2/drm/card0/card0-eDP-1
DEBUG: inspecting type of device: /dev/video0
DEBUG: inspecting type of device: /dev/video1
DEBUG: inspecting type of device: /dev/full
DEBUG: inspecting type of device: /dev/rfkill
DEBUG: cannot get major/minor numbers for syspath /sys/module/rfkill
DEBUG: associated snap application process 17530 with device cgroup snap.chromium.chromium
DEBUG: forked support process 17550
DEBUG: block device of snap core22, revision 867 is 7:1
DEBUG: sanity timeout initialized and set for 30 seconds
DEBUG: helper process waiting for command
DEBUG: sanity timeout initialized and set for 30 seconds
DEBUG: joining preserved mount namespace for inspection
DEBUG: found base snap device 7:1 on /usr
DEBUG: sanity timeout reset and disabled
DEBUG: preserved mount is not stale, reusing
DEBUG: joined preserved mount namespace chromium
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: moved process 17530 to cgroup hierarchy /sys/fs/cgroup/freezer/snap.chromium
DEBUG: releasing lock 7
DEBUG: sending command 0 to helper process (pid: 17550)
DEBUG: waiting for response from helper
DEBUG: sanity timeout reset and disabled
DEBUG: helper process received command 0
DEBUG: DEBUG: helper process exitingwaiting for the helper process to exit

DEBUG: helper process exited normally
DEBUG: resetting PATH to values in sync with core snap
DEBUG: -- snap startup {"stage":"snap-confine mount namespace finish", "time":"1698891102.233211"}
DEBUG: set_effective_identity uid:0 (change: yes), gid:0 (change: yes)
DEBUG: creating user data directory: /root/snap/chromium/2675
DEBUG: ruid: 0, euid: 0, suid: 0
DEBUG: loading bpf program for security tag snap.chromium.chromium
DEBUG: read 6064 bytes from /var/lib/snapd/seccomp/bpf//snap.chromium.chromium.bin
DEBUG: read 152 bytes from /var/lib/snapd/seccomp/bpf/global.bin
DEBUG: execv(/usr/lib/snapd/snap-exec, /usr/lib/snapd/snap-exec...)
DEBUG:  argv[1] = chromium
DEBUG: umask restored to  022
DEBUG: working directory restored to /home/wangyonggang
DEBUG: -- snap startup {"stage":"snap-confine to snap-exec", "time":"1698891102.234116"}
2023/11/02 10:11:42.240752 logger.go:92: DEBUG: -- snap startup {"stage":"snap-exec to app", "time":"1698891102.240743"}
cannot snap-exec: cannot exec "/snap/chromium/2675/snap/command-chain/desktop-launch": no such file or directory
wangyonggang@wangyonggang-pc:~$ sudo journalctl -b -u snapd
-- Logs begin at Thu 2023-10-12 18:45:43 CST, end at Thu 2023-11-02 10:12:19 CST. --
11月 02 08:58:23 wangyonggang-pc systemd[1]: Starting Snap Daemon...
11月 02 08:58:23 wangyonggang-pc snapd[1273]: AppArmor status: apparmor not enabled
11月 02 08:58:25 wangyonggang-pc snapd[1273]: overlord.go:272: Acquiring state lock file
11月 02 08:58:25 wangyonggang-pc snapd[1273]: overlord.go:277: Acquired state lock file
11月 02 08:58:25 wangyonggang-pc snapd[1273]: daemon.go:247: started snapd/2.60.4 (series 16; classic; devmode) kylin/v10 (arm64) linux/5.4.18-85-generic.
11月 02 08:58:25 wangyonggang-pc snapd[1273]: daemon.go:340: adjusting startup timeout by 1m10s (pessimistic estimate of 30s plus 5s per snap)
11月 02 08:58:25 wangyonggang-pc snapd[1273]: backends.go:58: AppArmor status: apparmor not enabled
11月 02 08:58:25 wangyonggang-pc systemd[1]: Started Snap Daemon.
11月 02 09:52:38 wangyonggang-pc runuser[24893]: pam_unix(runuser:session): session opened for user wangyonggang by (uid=0)
11月 02 09:52:38 wangyonggang-pc runuser[24923]: pam_unix(runuser:session): session opened for user wangyonggang by (uid=0)
11月 02 09:52:38 wangyonggang-pc runuser[24923]: pam_unix(runuser:session): session closed for user wangyonggang
11月 02 09:52:44 wangyonggang-pc runuser[24893]: pam_unix(runuser:session): session closed for user wangyonggang

Thanks for any idea.