Open rmpinchback opened 1 year ago
Same as all the above as well, even --classic
doesn't help. I can manually assigned an AppArmor profile but that's supposed to be done by snap based on information given by the program build to know what to access, so I'm guessing something is incomplete there?
Same issue for me... Is there a workaround? snap connect nvtop:kubernetes-support
also doesn't work for me. Running Ubuntu 22.04.4 and installed nvtop via snap.
It looks like @Syllo might have removed it on this commit: https://github.com/Syllo/nvtop/commit/4c471b19e5b447c6007be5ac3f098097885edcc7#diff-56759910381a014fecfd7556dd72ddd68c747d922a5b7df2044b9ce7c552f5f5L26-R29
IDK why it was removed, but I'm getting the same errors on my install too... I'd imagine if @Syllo wanted to add it back they could just un-comment & do another release.
From
dmesg | grep nvtop
:The /proc/$NNNN/fdinfo lines repeat extensively.
From
lsb_release -a
:From
uname -a
(note, I removed the actual hostname below):I'm new to using nvtop so I'm not sure what exactly might be breaking. The only problem I've seen so far is that the README.md doc says to do
snap connect nvtop:kubernetes-support
after the snap installation, but that generates the error: