[Bug 1640514] Re: /snap/bin is not added to the PATH when using zsh
Michael Stucki
mundaun at gmx.ch
Wed May 1 09:05:33 UTC 2019
The fix by @dolphytr works, but it's still incomplete. It helps to bring
back apps to the menu, but they still can't be run from the command
line. For this to work, I had to apply the commands from #18 plus add
these two lines to my $HOME/.zshrc:
# Fix environment for Wayland + zsh + snapd
source /etc/profile.d/apps-bin-path.sh
As these are just workarounds, the root of the problem seems to be
somewhere else:
The script in /etc/profile.d/apps-bin-path.sh takes care of all the
neccessary changes. It is sourced when starting an X11 session but not
when starting a Wayland session (at least not in combination with zsh).
I suggest to reopen this ticket until that's solved.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to zsh in Ubuntu.
https://bugs.launchpad.net/bugs/1640514
Title:
/snap/bin is not added to the PATH when using zsh
Status in Snappy:
Fix Released
Status in snapd package in Ubuntu:
Confirmed
Status in zsh package in Ubuntu:
Invalid
Status in snapd source package in Xenial:
Confirmed
Status in zsh source package in Xenial:
Invalid
Status in snapd source package in Bionic:
Fix Released
Status in zsh source package in Bionic:
Invalid
Bug description:
--- Environment ---
Ubuntu Zesty 17.04 (dev)
zsh
snapd 2.16
--- Description ---
zsh does not seem to load the scripts in /etc/profile.d/ (see https://bugzilla.redhat.com/show_bug.cgi?id=88457 ).
As a consequence, /snap/bin is not added to PATH, and running snaps from terminal (without snap run) does not work
--- How to reproduce ---
1) Install zsh
2) try running apps provided by snaps from the shell, without using snap run
To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1640514/+subscriptions
More information about the foundations-bugs
mailing list