Bug#909395: upgrade-reports: missing sbin in root path

[Jeff Cliff]

Package: upgrade-reports
Severity: important

Dear Maintainer,

Not really sure where to submit this but upgrading to buster via instructions at
https://wiki.debian.org/DebianTesting
resulted in a system that would boot fine, but when i went back in to aptitude afterwards I noticed
/sbin (and its subdirectories, eg /usr/local/sbin:/usr/sbin:/sbin ) was not in root's path. This meant
if I used 'su' to log in to root, to install/upgrade/whathaveyou ...ldconfig, 'shutdown' among other
things was not in the path.

I've now upgraded 2 systems from stable to buster and both did the same thing.

adding

PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin

to .bashrc for root (which was empty) made at least installing/upgrading via aptitude work...but there
wasn't much indication that I had to do this anywhere.

If this is something new that we have to do for buster, it should be in the instructions

-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

[Niels Thykier]

Control: tags -1 moreinfo

Post by Jeff Cliff
Package: upgrade-reports
Severity: important
Dear Maintainer,
Not really sure where to submit this but upgrading to buster via instructions at
https://wiki.debian.org/DebianTesting
resulted in a system that would boot fine, but when i went back in to aptitude afterwards I noticed
/sbin (and its subdirectories, eg /usr/local/sbin:/usr/sbin:/sbin ) was not in root's path. This meant
if I used 'su' to log in to root, to install/upgrade/whathaveyou ...ldconfig, 'shutdown' among other
things was not in the path.
I've now upgraded 2 systems from stable to buster and both did the same thing.
adding
PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin
to .bashrc for root (which was empty) made at least installing/upgrading via aptitude work...but there
wasn't much indication that I had to do this anywhere.
If this is something new that we have to do for buster, it should be in the instructions
[...]

Hi Jeff,

Are you perhaps using "su" (instead of "su -") when changing to root?
If so, then there is a Stretch -> Buster specific change specifically
for "su" about that in util-linux's NEWS file. It will probably be
written in the release-notes for buster (once we start writing those for
buster).

I can recommend using "apt-listchanges", which will show the NEWS files
of packages on upgrades.

Thanks,
~Niels

[Lars Henrik Ørn]

Hi


I have the same problem. I have for long periods been running Buster.
Until lately with xfce as enviroment. Recently I had a problem and
reeinstalled all over. I am now running with Gnome. If I am runing the
desktop (as I said Gnome) I am not able to get the full path, either
from gnome or tty until I log out. After log out and then logging into a
tty everything is working as expected.


So gnome is under startup declaring its own path somewhere, and it is
then broken until you log out from the desktop. This and its auto update
feature (once a day) is current serious gnome problems.

I have no clue about what part of gnome is responsible for this.

[Debian Bug Tracking System]

Post by Niels Thykier
tags -1 moreinfo

Bug #909395 [upgrade-reports] upgrade-reports: missing sbin in root path
Added tag(s) moreinfo.