Wow! This puzzled me for a while.
On a fresh Ubuntu Server 18.04 install. snap up to date. It turns out that in
my case, the issue was caused by a change in Debian's default behavior of the
su command.
https://unix.stackexchange.com/questions/460478/debian-su-and-su-path-differences
Since
I can confirm it did work for some time but has regressed lately in
20.04.
The snap paths are missing from environment when login shell is
/usr/bin/fish
pmart@t420 ~> systemctl show-environment --user | grep -e '^PATH' -e '^XDG_DATA'
Is this still a problem. The 2.41 release is out in the wild for a while
now.
Dear reporter, can you still reproduce the issue with the Debian package
of snapd 2.41?
** Changed in: snapd
Status: In Progress => Fix Released
** Changed in: snapd (Ubuntu)
Status: In Progress =>
This sounds like the fish shell maybe does do something fishy (sry for
the pun) with the /etc/environment. In snapd 2.41 we use a systemd
generator to create the right PATH on bootup, so this version (which wil
be availalbe as a deb in *-updates shortly) should fix this issue.
** Changed in:
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832675
Title:
On a fresh install of Kubuntu and fish shell my snaps are not in PATH
Could be the same as https://github.com/snapcore/snapd/pull/6813
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832675
Title:
On a fresh install of Kubuntu and fish shell my snaps are not in PATH
** Description changed:
- /snap/bin is not in PATH. My default shell is Fish
+ I get the following error when trying to launch any downloaded snaps
+ (e.g. Slack, Hexchat, etc.). I'm using Fish shell as default
+
+ ```
+ The command could not be located because '/snap/bin' is not included in the
