Re: A .profile puzzle

[Greg Wooledge <greg@wooledge.org>]

On Mon, Oct 18, 2021 at 08:56:47AM -0400, Gene Heskett wrote:
> On Monday 18 October 2021 07:17:05 Greg Wooledge wrote:
> 
> > On Mon, Oct 18, 2021 at 01:42:43AM -0400, Gene Heskett wrote:
> > > On Monday 18 October 2021 01:12:42 Will Mengarini wrote:
> > > > * Gene Heskett <gheskett@shentel.net> [21-10/17=Su 12:18 -0400]:
> > > > > [...] opening a terminal hasn't called
> > > > > a ". .profile" since about jessie [...]
> > > >
> > > > Check whether you *also* have either .bash_profile or
> > > > .bash_login, because either of those supersedes .profile:
> > > >
> > > > ls -lA ~/.bash_{profile,login}
> > >
> > > Neither present, just .bashrc, and .bash_logout
> >
> > That's as expected, then.  Your .profile is not being read *now*
> > because it's not supposed to be, if you use a Display Manager to
> > login.
> >
> > Your .profile *used* to be read by terminals, because previously, your
> > terminals had been configured to run login shells.  However, I'd bet
> > it was *not* read by your session, meaning any changes to the
> > environment would not be seen by graphical applications that you
> > launched directly from your Desktop or your WM, without going through
> > a terminal.
> >
> > Assuming you run a Debian X11 Session via a Display Manager, and also
> > assuming you don't have a .xsession file, you probably want to
> > configure your environment in ~/.xsessionrc (note the "rc" on the
> > end).
> 
> That does not exist on that machine. I'll look into it a bit later, 
> thanks Greg.

Create it.  Now it exists.  Tada!