Does not warn when /snap/bin is not in the path
Bug #1593157 reported by
Stuart Bishop
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| snapd |
Confirmed
|
High
|
Unassigned | ||
Bug Description
Snaps fail to run when /snap/bin is not in the path. For example, the 'hello world' tour on snapcraft.io fails when a user has just installed snapd for the first time, as they need to relogin or otherwise fix their $PATH. This is non-obvious to new users, who will likely assume binaries get placed or linked to standard locations such as /usr/bin or /usr/local/bin.
The snap cli tool could detect and warn in this case to improve a users first impressions.
Revision history for this message
| Zygmunt Krynicki (zyga) wrote | #1 |
| Changed in snappy: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
Revision history for this message
| Trent Lloyd (lathiat) wrote | #2 |
| summary: |
- Does not warn whe /snap/bin is not in the path + Does not warn when /snap/bin is not in the path |
Revision history for this message
| Liam Galvin (liamg87) wrote | #3 |
Revision history for this message
| Liam Galvin (liamg87) wrote | #4 |
| affects: | snappy → snapd |
To post a comment you must log in.
Hey. Good catch, thanks for reporting this. I think it can be easily changed with a patch to cmd/snap/ package. Are you interested in working on fixing this (with mentoring if required)?