Hello I was able to solve the problem By following these steps (1,2,3) First: writing the following command $systemctl status snapd.service output well be like { $ systemctl status snapd.service ● snapd.service - Snap Daemon Loaded: loaded (/usr/lib/systemd/system/snapd.service; disabled; vendor preset: disabled) Active: inactive (dead) TriggeredBy: ● snapd.socket } Now we write the following command $systemctl start snapd.service it ask you for root password And for sure $systemctl status snapd.service output well be like {" $ systemctl status snapd.service ● snapd.service - Snap Daemon Loaded: loaded (/usr/lib/systemd/system/snapd.service; disabled; vendor preset: disabled) Active: active (running) since Wed 2020-06-10 13:34:31 EEST; 18min ago TriggeredBy: ● snapd.socket Main PID: 3462 (snapd) Tasks: 11 (limit: 6923) Memory: 45.0M CPU: 917ms CGroup: /system.slice/snapd.service └─3462 /usr/libexec/snapd/snapd
Jun 10 13:34:30 dhcppc7 systemd[1]: Starting Snap Daemon...
Jun 10 13:34:30 dhcppc7 snapd[3462]: AppArmor status: apparmor not enabled
Jun 10 13:34:31 dhcppc7 snapd[3462]: daemon.go:343: started snapd/2.45-1.fc32 (series 16; classic; devmode) f>
Jun 10 13:34:31 dhcppc7 snapd[3462]: daemon.go:436: adjusting startup timeout by 50s (pessimistic estimate of>
Jun 10 13:34:31 dhcppc7 systemd[1]: Started Snap Daemon.
Jun 10 13:34:42 dhcppc7 snapd[3462]: storehelpers.go:438: cannot refresh: snap has no updates available: "cor>
Jun 10 13:34:42 dhcppc7 snapd[3462]: autorefresh.go:397: auto-refresh: all snaps are up-to-date
[loaialnshar@localhost ~]$
"} Now everything is ready for action Note:You need to do this every time after turning on the computer And I work on Fedora 32 KDE