I looked for where this $PATH was set from - and
it was not in the users $HOME
the place I found it in was /etc/profile.d/home-local-bin.sh
and
LANG=C pacman -Qo /etc/profile.d/home-local-bin.sh
/etc/profile.d/home-local-bin.sh is owned by filesystem 2022.06.08-3
shows that this comes from the package “filesystem”
But I do not see that package being in any recent update - so:
the file should still be there and the $PATH still be set from it
unless you made some change to the config files in your $HOME
This is a recent install of Manjaro Xfce - using bash everywhere
while I know that Plasma uses zsh in it’s default terminal.
Perhaps it’s due to that …?
Maybe the .local/bin was not in .bashrc but somewhere else, so that somewhere else got edited or removed hence removed from PATH also… but .bashrc does not look like was edited according to last modification time.
Directory /home/user/.dotnet/tools, which belongs to user, is in root path.
Also it’s not working as intended since the .local/bin is not in path for either user or root.
If it is in root’s $PATH - it can only be from some shell configuration file in /root directory
or - rather unlikely - somewhere in /etc
If this is the response that you get when you issue: sudo -i
Nothing in /root or in $HOME is ever touched by anything that is installed
Only /etc is a possible source.
→ you should be able to search through /root (or /etc) for that expression
(or just the first part of it)
to find the file where it is set
it has got to be somewhere
Normally, nothing is printed when you issue: sudo -i
The only thing that is in the same named file on my system is:
I cannot imagine where the difference between your file and my file may come from.
… it is not like this in the “filesystem” package where it originates from.
This has got to be a change made by you - perhaps inadvertently.
Are you sure your system is up to date - and you don’t have any *.pacnew files?
It is possible - but unlikely - that some AUR package … replaced it.
What is in your file … is not in the original file from the original package.
and if it got replaced for some reason, pacman would have written a .pacnew file of the same name
… actually: no - wrong assessment …
the file would have stayed as it was - and a .pacnew file created with the alternate content
and unless you merged it/replaced it - it would still be the same as the original
Did you notice in the commit notes it closes Issue #4? Have you read it?
Folks, this change is only applicable to filesystem 2022.10.08-1 in the unstable branch.
@Tribble Since you’re obviously using the unstable branch, it would have been very helpful to mention that and use the #unstable tag in your thread so others know. Your profile states you’re using the stable branch. Might want to keep that up to date.
FYI, there have been no changes to my $PATH after the 2022.10.08-1 update to filesystem on two machines.