Should not ~/bin be included in path when running via VNC?

[Bo Berglund]

On Sat, 23 May 2020 17:38:32 -0400, Sheemon Lists
<sheemon.lists at gmail.com> wrote:

>On Sat, May 23, 2020, 16:22 Bo Berglund <bo.berglund at gmail.com> wrote:
>
>> I am baffled by a strange situation:
>> Laptop with Ubuntu 18.04.4 LTS with the Mate desktop
>>
>> If I access the system through PuTTY all executables inside ~/bin are
>> available for use.
>>
>> But when I access the machine via VNC and use a Terminal window on the
>> desktop, then ~/bin is strangely not on path so none of the
>> executables are directly accessible. I have to always include the
>> ~/bin/ in front of them.
>>
>> What causes this?
>>
>
>Profile vs. bashrc, in /etc, in tilde.
>PATH is a convention, and different people at different times arrive at
>different interpretations.

I do not understand your comment here....

What I am talking about is one and the same physical computer accessed
in the following two ways:

1) SSH terminal session using PuTTY on a Windows machine

2) VNC GUI session from gthe same Windows machine in which a terminal
window is opened (directly inside Ubuntu)

In case 1) I get access to files inside ~/bin but in case 2) these
files are not accessible unless a full path is provided.

So I am talking about a single Ubuntu system acting up depending on
how I get to a terminal window on the same.

>> Note: On Raspbian via VNC this works as it should, i.e. a terminal
>> window on the GUI has ~/bin on path like PuTTY has.

I have an RPi4 with Raspbian Buster and VNC installed (this is a
different Linux system, still Debian based).

On this I do not get the different results for 1) and 2) above, both
act the same, i.e. I get access to the ~/bin dir without having to
enter the path in the commands.

To my knowledge I have not done anything different between the two
systems installation-wise and still they behave so differently.


-- 
Bo Berglund
Developer in Sweden