Does not warn when /snap/bin is not in the path

Bug #1593157 reported by Stuart Bishop on 2016-06-16
This bug affects 3 people
Affects Status Importance Assigned to Milestone

Bug Description

Snaps fail to run when /snap/bin is not in the path. For example, the 'hello world' tour on 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.

Zygmunt Krynicki (zyga) wrote :

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)?

Changed in snappy:
status: New → Confirmed
importance: Undecided → High
Trent Lloyd (lathiat) wrote :

I have filed a new but related bug here

/snap/bin is not added to path for "sudo su"

Chad Smith (chad.smith) on 2016-10-21
summary: - Does not warn whe /snap/bin is not in the path
+ Does not warn when /snap/bin is not in the path
Liam Galvin (liamg87) wrote :

I'll have a bash at this as a good first issue.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers