Sudden strangeness in PATH
Sudden strangeness in PATH
I have suddenly found that /usr/games has disappeared off my path. Not only that but my normal otherwise but sudo enabled user seems to have a superuser's path?
rhudson@adam:~$ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
rhudson@adam:~$ id -u 1000
What would have changed suddenly? It was not like this yesterday. kpat is in /usr/games and I was able to launch it from task manager yesterday, but not today.
I have rebooted twice so far. I can run kpat by opening it from Dolphin.
I don't want to have to re-install : ^ (
You're viewing a single thread.
Check your ~/.bash_profile, ~/.bashrc, and ~/.profile files. See if they were modified. You can add those paths (~/bin, /usr/games) to one of those files: export PATH=$PATH:~/bin:/usr/games
I have included this line in my .bash_profile:
export PATH="$HOME/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
In the very last line.
My PATH still looks like this:
rhudson@adam:~$ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
What could be changing my path after .bash_profile gets its say?
I am also adding it now to the last line of .bashrc
I have rebooted and now my path seems correct:
rhudson@adam:~$ echo $PATH /home/rhudson/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
I can type "kpat" at the command line and it launches.
But when I click the icon in the task manager it still says it can't find the program 'kpat'
Depending on how you're starting X (assuming X and not Wayland), you could add a line to your ~/.xprofile (or .xsession or .xinitrc) with ". ~/.bashrc" to make sure the path gets set before launching X.
The issue shows up under Wayland, not X. With X everything is working ok. I have yet to try a different Task Manager under Wayland though.
So I would look into how to make sure Wayland apps inherit your ~/.bashrc settings
I took a moment to swich back to wayland, and tried "Task Manager" (I was using "Icons only Task Manager") both are showing this issue which is resolved by switching back to X.