Strange PATH on one install

This forum is dedicated to advanced help and support :

Ask here your questions about advanced usage of Mageia. For example you may post here all your questions about network and automated installs, complex server configurations, kernel tuning, creating your own Mageia mirrors, and all tasks likely to be touchy even for skilled users.

Strange PATH on one install

Postby ncarver » Aug 14th, '20, 04:51

I recently installed MGA7.1 on three machines. With the two laptops where I used the plasma live installer, I end up with reasonable PATH after graphical login:
Code: Select all
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/usr/lib64/qt5/bin:/usr/lib64/qt4/bin:/home/carver/.local/bin:/home/carver/bin


However, on the desktop where I used the traditional installer, I found that I ended up with a very different and rather strange PATH after graphical login:
Code: Select all
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/usr/lib64/qt5/bin:/usr/lib64/qt4/bin


I don't understand why the sbin entries are in my normal non-root user PATH, and the ~/.local/bin and ~/bin are missing, even though they are supposed to be added by ~/bash_profile.

I note that SSH'ing into the desktop yields a reasonable PATH:
Code: Select all
/usr/local/bin:/usr/bin:/usr/local/games:/usr/games:/usr/lib64/qt5/bin:/usr/lib64/qt4/bin:/home/carver/.local/bin:/home/carver/bin


So this seems to be an issue related to how the DM is starting things. I noticed that the desktop was using gdm while the two laptops were using sddm, but changing the desktop to use sddm did not fix PATH.

Would appreciate suggestions about what might be causing this or at least what differences I might look for between the installs.
ncarver
 
Posts: 19
Joined: May 25th, '11, 18:23

Return to Advanced support

Who is online

Users browsing this forum: No registered users and 1 guest