Hi Gunnar,
maybe I missed that ubuntu does interpret the meaning of /sbin
differently than the classic UNIX systems. In that case I'd fix it in my
.bashrc.
I really would be interested in a statement of an experienced ubuntu
developer about such a decission and the reasons for it.
Anyway I'm a
The patch in #9 doesn't fix it completely for me, as also some of the
scripts in /usr/share/upstart/sessions/* assume that /sbin is in $PATH.
Some of them call initctl which resides in /sbin
Unfortunately this means that a lot of packages would need to be fixed.
A grep-loop-dpkg -S-awk-sort-uniq
** Description changed:
- According to changelog.Debian lightdm is using bash for the session to
- improve error handling to fix #678421.
+ According to changelog.Debian from version 1.12.3 on lightdm is using
+ bash for the session to improve error handling to fix #678421.
Unfortunately
** Description changed:
According to changelog.Debian from version 1.12.3 on lightdm is using
bash for the session to improve error handling to fix #678421.
Unfortunately this can break the session start up when the user sets the
$PATH environment variable in ~/.bashrc. Then /sbin
When I was young I've been taught that the sbin dirs are not supposed to
be in the user's $PATH, but only in the superuser's. (the s in /sbin
stands for superuser). Usually in the sbin dirs are only tools you
need for sysadmin tasks. So it is a good idea not to have it in the
$PATH of an ordinary
Public bug reported:
According to changelog.Debian lightdm is using bash for the session to
improve error handling to fix #678421.
Unfortunately this can break the session start up when the user sets the
$PATH environment variable in ~/.bashrc. Then /sbin might no longer be
in $PATH and
6 matches
Mail list logo
