Update 6/2/2020
Uninstalled and re-installed and got hello-world! to work. So i went deeper in the rabbit hole, found and tried:
-
sudo dpkg --configure -a
from launch pad snappy bug# 1693037 -
sudo apparmor_parser --replace --write-cache /etc/apparmor.d/usr.lib.snapd.snap-confine.real --cache-loc /etc/apparmor.d/cache
from https://askubuntu.com/questions/989389/cannot-run-snap-app -
found # re mount -t overlay -o “upperdir=$tmpfs/up,lowerdir=$src,workdir=$tmpfs/work” overlay “$dst”
from: Snaps don't run in the new LTSP
…i’m holding off on trying this fix until i understand how it works or someone advises it is likely the fix needed for the original
-cannot create lock directory /run/snapd/lock issue posted
(fix #3 looks like it could break the system if applied inappropriately …usually unix/linux has a risky complex route and a simpler basic logic route…)
It is difficult to imagine the root overlay system alone is at fault. Snaps work fine for 32 bit on the same desktop environment, same distributions and machines, same root overlay persistence setup. It is as if snapd needs access that the 64bit architecture is not allowing. (chmod to the /snapd/lock file has no effect)