Bug#460820: x11-common: no login shell run when logging in through gdm

["Michal Suchanek" <hramrach@centrum.cz>]

On 15/01/2008, Brice Goglin <Brice.Goglin@ens-lyon.org> wrote:
> Please keep the bug in CC when replying.
>
>
>
> Michal Suchanek wrote:
> > It's the config for my shell. I (or rather the maintainer of bash or
> > base-files in this case) put that stuff into .bash_profile to be
> > executed when I log in.
> >
>
> If it's the config for your shell, it goes in the config file for the
> shell. It doesn't have to be loaded anywhere else.

OK, then what is the config file where I configure my path for any
session X or console?

Perhaps this is too general to be solved in this package.

>
> > I do not want this to be a variable for my X clients. I want it to be
> > a variable for my login sessions, graphical or not.
>
> What do you mean login session? Your .xsession script? Just use the
> right shell in .xsession, it will load its config file, you will get
> your environment as in any instance of the shell.

Login session is the stuff that gets executed after I sucessfully
authenticate (log in) to the system. This is currently possible to do
through login (/bin/login) or *dm (like xdm or gdm).

>
> >  I cannot put it
> > into .bashrc because it would probably not get executed for the X
> > session anyway, and my path would probably grow insanely in every make
> > script as nested shells are executed. Even the bash man page advises
> > against that.
> >
>
> Also, you can put your environment definitions in a random script and
> source it from both .bashrc and .xsessionrc.

Yes I have to fix the scripts on every system. And think about what
stuff gets where if I do not want to break anything. That's what I
would like to avoid.

>
> Our Xsession already does everything needed here, so I am closing this bug.

Yes, the .xsessionrc support is certainly an improvement.

Thanks

Michal