16.04.3 deployments include non-existent directories in $PATH
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bash (Ubuntu) |
Opinion
|
Low
|
Unassigned | ||
snapd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Noticed this while doing regression testing on 16.04.3, and a number of customers have asked with concerns as well during their testing.
I don't know exactly when this started, but we just started noticing it with 16.04.3 (4.10) but $PATH by default now includes several directories that do not exist:
ubuntu@above-ox:~$ find $(echo "$PATH" | sed -e 's/:/ /g') -maxdepth 1 -type d
find: ‘/home/ubuntu/bin’: No such file or directory
find: ‘/home/
/usr/local/sbin
/usr/local/bin
/usr/sbin
/usr/bin
/sbin
/bin
/usr/games
/usr/local/games
find: ‘/snap/bin’: No such file or directory
We noticed this because it was causing a resource job in the certification suite to suddenly start failing (the failure was not catastrophic, but it did appear to customers who were concerned.
I've verified this on both s390x and amd64 16.04.3 deployments via MAAS 2.2.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-
ProcVersionSign
Uname: Linux 4.10.0-32-generic s390x
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: s390x
Date: Wed Aug 16 18:59:34 2017
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en.US_UTF-8
SHELL=/bin/bash
SourcePackage: linux-hwe
UpgradeStatus: No upgrade log present (probably fresh install)
description: | updated |
Changed in snapd (Ubuntu): | |
status: | New → Invalid |
Changed in bash (Ubuntu): | |
status: | Triaged → Opinion |
~/bin ~/.local/bin used to be added in a user path only if they exist.
/snap/bin may or or may not exist, but could be a bug in snapd.