Hello! I encountering very strange behavior of my ubuntu 19.10. When I recomplie my snapd to solve xdg-open issues (basically allows everything) I stuck to get my resulting /usr/bin/snap to work.
I changed it, compiled it, install it and got no changes. Still unable to open xdg-open to work. I dig deeper. I change default snap “help” cmd output to “refresh !!! and remove snaps” added three excalamation marks. Then reinstall package… still no changes. Then I checked if my deb package containing correct file and got surprized, since when I run unpacked deb snap 123/usr/bin/snap I got my new out put with “refresh !!! and remove snaps”. So, I compared two files md5 sum unpacked and installed:
axet@axet-laptop:~/local$ ./123/usr/bin/snap
The snap command lets you install, configure, refresh !!! and remove snaps.
Snaps are packages that work across many different Linux distributions,
enabling secure delivery and operation of the latest apps and utilities.
axet@axet-laptop:~/local$ /usr/bin/snap
The snap command lets you install, configure, refresh and remove snaps.
Snaps are packages that work across many different Linux distributions,
enabling secure delivery and operation of the latest apps and utilities.
That very confusing. Even when I copy /usr/bin/snap into 111111 then run 111111 I’m getting the correct output with “!!! and remove snaps”. Seems like when I ran snap I got one binary image, but when I read the same file I get different image. Look like virus, kernel, hardware or encryption bug. I’m running Ubuntu 19.10 with luks/lvm encryption.
I also tied to put simple “hello world” into /usr/bin/snap and get “hello world” output. But when I install snapd I always get “old” version.
Any one faced something like this? Maybe it is CPU bug, which caching something?
The snap command will re-execute itself into the version from the core snap or the snapd snap if the version number there is higher. Try setting the env var SNAPD_REEXEC=0 when running snap ... and see if that makes it work the way you expect.
Thank you for letting me know my system is not compromised. But It is very unpleasant to know this is the build-in feature. But, I still unable to run my original binary even when I run:
Sorry I don’t quite follow, are you saying that re-exec isn’t working? To make things clear let’s figure out where all of the possible “snap” binaries that your system could be re-execing to. What is the output of:
I want to remove restriction to xdg-open, and allow all protocols redirected to the system level. To do I rebuild snapd as deb file and install it. I unable to use it, since snap does not allow me to run it!
