Mount snap "snapd" (10492) ([start snap-snapd-10492.mount] failed with exit status 1: Job failed. See "journalctl -xe" for details

Hi there.
I am on Garuda linux. When I want to install any types of snap pack, it stop with this error.

Mount snap “snapd” (10492) ([start snap-snapd-10492.mount] failed with exit status 1: Job failed. See “journalctl -xe” for details.

How can I fix it?

What is journalctl --no-pager -u snap-snapd-10492.mount and journalctl --no-pager -u snapd ?

journalctl --no-pager -u snap-snapd-10492.mount

– Journal begins at Thu 2021-01-14 08:52:56 +06, ends at Thu 2021-01-14 08:56:24 +06. –
– No entries –

journalctl --no-pager -u snapd

– Journal begins at Thu 2021-01-14 08:52:56 +06, ends at Thu 2021-01-14 08:58:06 +06. –
Jan 14 08:52:59 nazmul-hpprobook450g2 systemd[1]: Starting Snap Daemon…
Jan 14 08:52:59 nazmul-hpprobook450g2 snapd[599]: AppArmor status: apparmor not enabled
Jan 14 08:52:59 nazmul-hpprobook450g2 snapd[599]: daemon.go:347: started snapd/2.48.2-1 (series 1
6; classic; devmode) garuda/ (amd64) linux/5.10.6-110-tkg-bmq.
Jan 14 08:52:59 nazmul-hpprobook450g2 snapd[599]: daemon.go:440: adjusting startup timeout by 30s
(pessimistic estimate of 30s plus 5s per snap)
Jan 14 08:52:59 nazmul-hpprobook450g2 snapd[599]: helpers.go:105: error trying to compare the sna
p system key: system-key missing on disk
Jan 14 08:52:59 nazmul-hpprobook450g2 systemd[1]: Started Snap Daemon.
Jan 14 08:53:00 nazmul-hpprobook450g2 snapd[599]: stateengine.go:150: state ensure error: Get “ht
tps://api.snapcraft.io/api/v1/snaps/sections”: dial tcp: lookup api.snapcraft.io: no such host
Jan 14 08:53:04 nazmul-hpprobook450g2 snapd[599]: daemon.go:589: gracefully waiting for running h
ooks
Jan 14 08:53:04 nazmul-hpprobook450g2 snapd[599]: daemon.go:591: done waiting for running hooks
Jan 14 08:53:04 nazmul-hpprobook450g2 snapd[599]: daemon stop requested to wait for socket activa
tion
Jan 14 08:53:04 nazmul-hpprobook450g2 systemd[1]: snapd.service: Succeeded.
Jan 14 08:53:47 nazmul-hpprobook450g2 systemd[1]: Starting Snap Daemon…
Jan 14 08:53:47 nazmul-hpprobook450g2 snapd[1979]: AppArmor status: apparmor not enabled
Jan 14 08:53:47 nazmul-hpprobook450g2 snapd[1979]: patch.go:64: Patching system state level 6 to
sublevel 1…
Jan 14 08:53:47 nazmul-hpprobook450g2 snapd[1979]: patch.go:64: Patching system state level 6 to
sublevel 2…
Jan 14 08:53:47 nazmul-hpprobook450g2 snapd[1979]: patch.go:64: Patching system state level 6 to
sublevel 3…
Jan 14 08:53:47 nazmul-hpprobook450g2 snapd[1979]: daemon.go:347: started snapd/2.48.2-1 (series
16; classic; devmode) garuda/ (amd64) linux/5.10.6-110-tkg-bmq.
Jan 14 08:53:47 nazmul-hpprobook450g2 snapd[1979]: daemon.go:440: adjusting startup timeout by 30
s (pessimistic estimate of 30s plus 5s per snap)
Jan 14 08:53:47 nazmul-hpprobook450g2 systemd[1]: Started Snap Daemon.
Jan 14 08:53:47 nazmul-hpprobook450g2 snapd[1979]: api.go:1007: Installing snap “hello-world” rev
ision unset
Jan 14 08:53:59 nazmul-hpprobook450g2 snapd[1979]: stateengine.go:150: state ensure error: decode
new commands catalog: net/http: request canceled (Client.Timeout or context cancellation while r
eading body)
Jan 14 08:54:56 nazmul-hpprobook450g2 systemd[1]: snapd.service: Got notification message from PI
D 2702, but reception only permitted for main PID 1979
Jan 14 08:54:56 nazmul-hpprobook450g2 snapd[1979]: taskrunner.go:271: [change 2 “Mount snap “cor
e” (10583)” task] failed: [start snap-core-10583.mount] failed with exit status 1: Job failed. S
ee “journalctl -xe” for details.
Jan 14 08:54:58 nazmul-hpprobook450g2 snapd[1979]: handlers.go:496: Reported install problem for
“core” as Crash report successfully submitted.
Jan 14 08:57:25 nazmul-hpprobook450g2 snapd[1979]: api.go:1007: Installing snap “hello-world” rev
ision unset
Jan 14 08:57:29 nazmul-hpprobook450g2 snapd[1979]: taskrunner.go:271: [change 4 “Mount snap “cor
e” (10583)” task] failed: [start snap-core-10583.mount] failed with exit status 1: Job failed. S
ee “journalctl -xe” for details.
Jan 14 08:57:29 nazmul-hpprobook450g2 snapd[1979]: handlers.go:496: Reported install problem for
“core” as already-reported