Removing a snap with `snap remove <app>` doesn't remove everything

[Josh Arenson]

Example

1. Verify that the app isn't installed
josh@blackbox:~$ kcalc
The program 'kcalc' is currently not installed. You can install it by typing:
sudo apt install kcalc

2. Install the snap
josh@blackbox:~$ sudo snap install kcalc

// Ignore the fact that the kcalc snap is broken :-) (this occurs with all snaps)

3. Remove the snap
josh@blackbox:~$ sudo snap remove kcalc
kcalc removed

4. Verify the app isn't installed
josh@blackbox:~$ kcalc
bash: /snap/bin/kcalc: No such file or directory

Notice the behavior is inconsistent with step #1...

FURTHERMORE, installing kcalc via apt and then running it via the cli results in the same error as step #4 and the app fails to run.

[Kyle Fazzari (kyrofa)]

$ mkdir foo
$ touch foo/bar.sh
$ chmod a+x foo/bar.sh
$ export PATH=$PATH:$(pwd)/foo
$ bar.sh
$ rm foo/bar.sh
$ bar.sh
-bash: /tmp/foo/bar.sh: No such file or directory

This seems to be normal behavior to me. One's shell doesn't walk the $PATH every time if it already knows where the binary is. If you start a new session you'll be back to step #1.

[Seth Arnold (seth-arnold)]

This is a feature of your shell. You can run `hash -r` in bash to remove all saved command locations. Other shells may vary.

Thanks

[Carl Patenaude Poulin (carlpaten)]

Maybe the snap uninstaller could detect bash shells and run `hash $bin` for every binary associated with a package? It would be very convenient. Thanks in advance for your consideration.

[Zygmunt Krynicki (zyga)]

Hash is a built-in shell function. It cannot be invoked in one spot to take effect in existing shell processes.