Misleading warning about /snap/bin not being in PATH

[Claudio Matsuoka]

The warning message "/snap/bin was not found in your $PATH. If you've not restarted your session since you installed snapd, try doing that." is issued in the situation the message describes, but also when /snap/bin is not in the secure path defined in /etc/sudoers. In the latter case the warning could be clearer about the real issue, telling the user that the directory is not in PATH when it actually is there is very confusing.

[Maciej Borzecki (maciek-borzecki)]

Which distro is that? We already automatically skip the warning on Fedora, Debian and openSUSE.

[Claudio Matsuoka (cmatsuoka)]

To clarify: the message is technically correct in the sense that the directory is not in PATH when executing the command with sudo, however trying to restart the session as directed doesn't work and the user may also verify his environment and see that the directory is already listed. In this case, stating that /snap/bin is not in the sudo secure path would be more informative.

[Claudio Matsuoka (cmatsuoka)]

This should happen in any distro using secure_path without listing /snap/bin, but it was specifically spotted in the Raspberry Pi OS.

[Launchpad Janitor (janitor)]

[Expired for snapd because there has been no activity for 60 days.]