Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #165786 > unrolled thread

User's bin path not recognised in login script

Back to article view | Back to linux.debian.user

Contents

  User's bin path not recognised in login script Russell Gadd <russ.mail.lists@gmail.com> - 2016-03-21 19:20 +0100
    Re: User's bin path not recognised in login script Sven Arvidsson <sa@whiz.se> - 2016-03-21 19:30 +0100
    Re: User's bin path not recognised in login script David Christensen <dpchrist@holgerdanske.com> - 2016-03-22 03:40 +0100
      Re: User's bin path not recognised in login script Russell Gadd <russ.mail.lists@gmail.com> - 2016-03-22 19:40 +0100
        Re: User's bin path not recognised in login script The Wanderer <wanderer@fastmail.fm> - 2016-03-22 20:00 +0100
          Re: User's bin path not recognised in login script Russell Gadd <russ.mail.lists@gmail.com> - 2016-03-22 23:50 +0100
            Re: User's bin path not recognised in login script The Wanderer <wanderer@fastmail.fm> - 2016-03-23 03:50 +0100
            Re: User's bin path not recognised in login script David Wright <deblis@lionunicorn.co.uk> - 2016-03-24 01:30 +0100
              Re: User's bin path not recognised in login script The Wanderer <wanderer@fastmail.fm> - 2016-03-24 01:40 +0100
              Re: User's bin path not recognised in login script Russell Gadd <russ.mail.lists@gmail.com> - 2016-03-24 09:30 +0100
        Re: User's bin path not recognised in login script Seeker <seeker5528@comcast.net> - 2016-03-22 21:20 +0100
          Re: User's bin path not recognised in login script Russell Gadd <russ.mail.lists@gmail.com> - 2016-03-22 23:50 +0100
        Re: User's bin path not recognised in login script Seeker <seeker5528@comcast.net> - 2016-03-22 22:10 +0100
        Re: User's bin path not recognised in login script Seeker <seeker5528@comcast.net> - 2016-03-22 22:30 +0100
        Re: User's bin path not recognised in login script seeker5528@comcast.net - 2016-03-22 22:50 +0100
          Re: User's bin path not recognised in login script Lisi Reisz <lisi.reisz@gmail.com> - 2016-03-23 00:00 +0100

#165786 — User's bin path not recognised in login script

The bash login script I have added in to my startup programs does not 
recognise /home/user/bin as part of the path, whereas it used to when I 
was running Linux Mint (I'm a recent refugee). I've got 
PATH="$HOME/bin:$PATH" in ~/.bashrc and also in ~/.profile, together 
with a ~/.bash_profile which sources ~/.profile. I've no idea whether 
all these are necessary - they do work to search my bin in a script run 
in the Mate terminal but not in the login script. It's not a big deal as 
I can prepend the absolute path in the login script, although I assume 
this means also doing it in sourced scripts within the login script, so 
I'd like to know if there's a clean way to set this up.

[toc] | [next] | [standalone]

#165787

[Multipart message — attachments visible in raw view] — view raw

On Mon, 2016-03-21 at 18:03 +0000, Russell Gadd wrote:
> The bash login script I have added in to my startup programs does
> not 
> recognise /home/user/bin as part of the path, whereas it used to when
> I 
> was running Linux Mint (I'm a recent refugee). I've got 
> PATH="$HOME/bin:$PATH" in ~/.bashrc and also in ~/.profile, together 
> with a ~/.bash_profile which sources ~/.profile. I've no idea
> whether 
> all these are necessary - they do work to search my bin in a script
> run 
> in the Mate terminal but not in the login script. It's not a big deal
> as 
> I can prepend the absolute path in the login script, although I
> assume 
> this means also doing it in sourced scripts within the login script,
> so 
> I'd like to know if there's a clean way to set this up.

If you are using gdm to launch X, /etc/gdm3/Xsession sources ~/.profile
other display managers probably do something similar.

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5

[toc] | [prev] | [next] | [standalone]

#165810

On 03/21/2016 11:03 AM, Russell Gadd wrote:
> The bash login script I have added in to my startup programs does not
> recognise /home/user/bin as part of the path, whereas it used to when I
> was running Linux Mint (I'm a recent refugee). I've got
> PATH="$HOME/bin:$PATH" in ~/.bashrc and also in ~/.profile, together
> with a ~/.bash_profile which sources ~/.profile. I've no idea whether
> all these are necessary - they do work to search my bin in a script run
> in the Mate terminal but not in the login script. It's not a big deal as
> I can prepend the absolute path in the login script, although I assume
> this means also doing it in sourced scripts within the login script, so
> I'd like to know if there's a clean way to set this up.


Did you remember the 'export' in .profile?

     export PATH=$PATH:$HOME/bin


It might help to add echo's in the various scripts to check the order in 
which they run -- e.g. verify that .bash_profile runs before your bash 
login script, so that PATH includes $HOME/bin.


David

[toc] | [prev] | [next] | [standalone]

#165833

On 22/03/16 02:40, David Christensen wrote:
> ...
>
> Did you remember the 'export' in .profile?
>
>      export PATH=$PATH:$HOME/bin
>
>
> It might help to add echo's in the various scripts to check the order in
> which they run -- e.g. verify that .bash_profile runs before your bash
> login script, so that PATH includes $HOME/bin.
>

Thanks for the export point which I have now used. However it doesn't 
solve the problem.

I experimented by adding the following line into ~/.bash_profile, 
~/.profile and ~/.bashrc:
echo "This is <scriptname>" &>>/tmp/out.txt

Neither of the profile files triggered the output, nor did .bashrc until 
I manually opened a Mate terminal from the desktop. So it appears that 
the profile files do not get invoked at any time.

I've even tried changing the PATH which is set at the top of 
/etc/profile, but this doesn't work either, so it looks like profile 
files are ignored altogether.

[toc] | [prev] | [next] | [standalone]

#165835

[Multipart message — attachments visible in raw view] — view raw

On 2016-03-22 at 14:20, Russell Gadd wrote:

> On 22/03/16 02:40, David Christensen wrote:

>> Did you remember the 'export' in .profile?
>>
>>      export PATH=$PATH:$HOME/bin
>>
>>
>> It might help to add echo's in the various scripts to check the
>> order in which they run -- e.g. verify that .bash_profile runs
>> before your bash login script, so that PATH includes $HOME/bin.
> 
> Thanks for the export point which I have now used. However it
> doesn't solve the problem.
> 
> I experimented by adding the following line into ~/.bash_profile,
> ~/.profile and ~/.bashrc:
> echo "This is <scriptname>" &>>/tmp/out.txt
> 
> Neither of the profile files triggered the output, nor did .bashrc
> until I manually opened a Mate terminal from the desktop. So it
> appears that the profile files do not get invoked at any time.

How did you test? By launching a new terminal (with bash set as your
default shell), by running the command 'bash' in an existing terminal,
by logging all of the way out (to the main login prompt, if not to a
full reboot) and then logging back in, or by running the command 'bash
--login' in an existing terminal?

In my testing just now, only the latter two of these four will pick up
the new ~/.profile file; the other two seem to run the commands which
were present in the file which their parent bash session used. (Strictly
speaking I didn't test the full logout or reboot, but I fully expect
that that would pick up the changes.)


Also, at least on my system, ~/.bashrc is invoked only by being sourced
from ~/.profile or ~/.bash_profile. Unless your system is configured
fairly differently, if ~/.bashrc is getting run, that means that - per
bash(1) - one of ~/.bash_profile, ~/.bash_login, or ~/.profile must be
invoking it.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

[toc] | [prev] | [next] | [standalone]

#165848

On 22/03/16 19:00, The Wanderer wrote:
> ... <see above>
>
> How did you test? By launching a new terminal (with bash set as your
> default shell), by running the command 'bash' in an existing terminal,
> by logging all of the way out (to the main login prompt, if not to a
> full reboot) and then logging back in, or by running the command 'bash
> --login' in an existing terminal?
>
> In my testing just now, only the latter two of these four will pick up
> the new ~/.profile file; the other two seem to run the commands which
> were present in the file which their parent bash session used. (Strictly
> speaking I didn't test the full logout or reboot, but I fully expect
> that that would pick up the changes.)
>
>
> Also, at least on my system, ~/.bashrc is invoked only by being sourced
> from ~/.profile or ~/.bash_profile. Unless your system is configured
> fairly differently, if ~/.bashrc is getting run, that means that - per
> bash(1) - one of ~/.bash_profile, ~/.bash_login, or ~/.profile must be
> invoking it.
>
I tested by rebooting each time. My ~/.bashrc is sourced from ~/.profile 
which itself is sourced from .bash_profile, but neither of them run the 
echo command I've added so I would assume the ~/.bashrc which runs when 
I open a Mate terminal is started some other way.

bash --login does invoke ~./bash_profile and hence ~./profile as the 
echos are seen in the output file (in the expected order), but I must 
admit the nature of login shells / non-login / interactive shells, etc 
is a bit beyond my experience. I've never tried bash --login before as I 
haven't previously come across it.

Maybe what this is telling me is that I should run another script from 
my "login" script by 'bash --login real_login_scriptfile' in order to 
get these profiles to run first?

[toc] | [prev] | [next] | [standalone]

#165853

[Multipart message — attachments visible in raw view] — view raw

On 2016-03-22 at 18:35, Russell Gadd wrote:

> On 22/03/16 19:00, The Wanderer wrote:

>> How did you test? By launching a new terminal (with bash set as
>> your default shell), by running the command 'bash' in an existing
>> terminal, by logging all of the way out (to the main login prompt,
>> if not to a full reboot) and then logging back in, or by running
>> the command 'bash --login' in an existing terminal?
>> 
>> In my testing just now, only the latter two of these four will pick
>> up the new ~/.profile file; the other two seem to run the commands
>> which were present in the file which their parent bash session
>> used. (Strictly speaking I didn't test the full logout or reboot,
>> but I fully expect that that would pick up the changes.)
>> 
>> 
>> Also, at least on my system, ~/.bashrc is invoked only by being
>> sourced from ~/.profile or ~/.bash_profile. Unless your system is
>> configured fairly differently, if ~/.bashrc is getting run, that
>> means that - per bash(1) - one of ~/.bash_profile, ~/.bash_login,
>> or ~/.profile must be invoking it.
> 
> I tested by rebooting each time. My ~/.bashrc is sourced from
> ~/.profile which itself is sourced from .bash_profile, but neither of
> them run the echo command I've added so I would assume the ~/.bashrc
> which runs when I open a Mate terminal is started some other way.
> 
> bash --login does invoke ~./bash_profile and hence ~./profile as the
>  echos are seen in the output file (in the expected order), but I
> must admit the nature of login shells / non-login / interactive
> shells, etc is a bit beyond my experience. I've never tried bash
> --login before as I haven't previously come across it.

Just as a stab in the dark: in a newly-launched terminal after a fresh
reboot, with no other commands run yet, what does 'echo $0' say?

There's a faint chance that your default shell isn't actually bash,
which would explain what you're seeing. I don't think that's very
likely, for multiple reasons, but it's easy enough to rule out.

> Maybe what this is telling me is that I should run another script
> from my "login" script by 'bash --login real_login_scriptfile' in
> order to get these profiles to run first?

I wouldn't advise that route, no. It might work, but it would be a
kludge at best, not a real solution.

Instead, assuming that the above test confirms that you are running bash
in these cases, I'd start out by going all the way to the top of the
stack and figuring out what scripts are calling what, to figure out how
~/.bashrc is getting invoked. Figuring that out should help figure out
what's going on, which should help get the rest to make sense.


Things to try include:

find ~/ -type f -maxdepth 1 -name ".*" -exec grep bashrc \;

grep -R bashrc /etc/bash*

strace -f bash --login 2>/tmp/bash.strace
[Ctrl-D]
(then search the resulting file for mentions of .bashrc, and look above
that to figure out which scripts were opened before opening .bashrc)

This last is the most complicated and hardest to understand, and I'm
pretty sure I haven't got the right strace command to get the most
information out of it anyway, but it should be enough to get things started.

You can also try searching the file for mentions of the profile files,
just in case they show up directly. (They should, in fact.)

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

[toc] | [prev] | [next] | [standalone]

#165884

On Tue 22 Mar 2016 at 22:35:32 (+0000), Russell Gadd wrote:
> On 22/03/16 19:00, The Wanderer wrote:
> >... <see above>
> >
> >How did you test? By launching a new terminal (with bash set as your
> >default shell), by running the command 'bash' in an existing terminal,
> >by logging all of the way out (to the main login prompt, if not to a
> >full reboot) and then logging back in, or by running the command 'bash
> >--login' in an existing terminal?
> >
> >In my testing just now, only the latter two of these four will pick up
> >the new ~/.profile file; the other two seem to run the commands which
> >were present in the file which their parent bash session used. (Strictly
> >speaking I didn't test the full logout or reboot, but I fully expect
> >that that would pick up the changes.)
> >
> >
> >Also, at least on my system, ~/.bashrc is invoked only by being sourced
> >from ~/.profile or ~/.bash_profile. Unless your system is configured
> >fairly differently, if ~/.bashrc is getting run, that means that - per
> >bash(1) - one of ~/.bash_profile, ~/.bash_login, or ~/.profile must be
> >invoking it.
> >
> I tested by rebooting each time. My ~/.bashrc is sourced from
> ~/.profile which itself is sourced from .bash_profile, but neither
> of them run the echo command I've added so I would assume the
> ~/.bashrc which runs when I open a Mate terminal is started some
> other way.

Take a look at   man bash   which will tell you that ~/.bashrc is run
whenever an interactive non-login bash is started. Opening a terminal
session with bash is exactly that.

> bash --login does invoke ~./bash_profile and hence ~./profile as the
> echos are seen in the output file (in the expected order), but I
> must admit the nature of login shells / non-login / interactive
> shells, etc is a bit beyond my experience. I've never tried bash
> --login before as I haven't previously come across it.

Normally, you don't have to run bash --login because it's done for you
by virtue of having /bin/bash in your line of /etc/passwd. However,
that presupposes you're logging in to a VC and then running X with the
startx command. It seems likely that you're not.

> Maybe what this is telling me is that I should run another script
> from my "login" script by 'bash --login real_login_scriptfile' in
> order to get these profiles to run first?

I don't know what you mean by   "login" script   because you haven't
yet told us (I believe) what your machine is configured to do when
you boot it up. If you've installed some sort of Desktop Environment,
then the DE has the responsibility of selecting the shell that runs
your   "login" script   and, indeed, what the filename of that script
is.

If that shell is not bash, then you should put all the environment
commands (basically anything that should only be executed once) in a
file that's *likely* to be called ~/.profile and the rest in
~/.bashrc. But you need to find out what the former should be
called by consulting the DE documentation.

Why .bashrc for a non-bash shell? Assuming you use bash as your
normal shell, you want all your functions and so on available.
However, a non-bash shell (like Debian's default dash shell) will
choke on bash's syntax as well as not being able to execute its
functions.

If you sometimes login with bash (eg remotely), then set your
~/.bash_profile to call both ~/.profile (for the one-off environment
stuff you've just set up) and ~/.bashrc (for the functions).

BTW bear in mind that some operations may be disrupted by having
startup files like .bashrc that aren't mute. It's probably not that
important while you're getting things sorted out, but you might want
to change them to something like this if you intend keeping things noisy:

[ -n "$PS1" ] && printf '%s\n' "(This is $HOME/.bash_profile 2015 July 13)"

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#165885

[Multipart message — attachments visible in raw view] — view raw

On 2016-03-23 at 20:23, David Wright wrote:

> On Tue 22 Mar 2016 at 22:35:32 (+0000), Russell Gadd wrote:
> 
>> On 22/03/16 19:00, The Wanderer wrote:

>>> Also, at least on my system, ~/.bashrc is invoked only by being
>>> sourced from ~/.profile or ~/.bash_profile. Unless your system is
>>> configured fairly differently, if ~/.bashrc is getting run, that
>>> means that - per bash(1) - one of ~/.bash_profile, ~/.bash_login,
>>> or ~/.profile must be invoking it.
>>> 
>> I tested by rebooting each time. My ~/.bashrc is sourced from 
>> ~/.profile which itself is sourced from .bash_profile, but neither 
>> of them run the echo command I've added so I would assume the 
>> ~/.bashrc which runs when I open a Mate terminal is started some 
>> other way.
> 
> Take a look at   man bash   which will tell you that ~/.bashrc is
> run whenever an interactive non-login bash is started. Opening a
> terminal session with bash is exactly that.

...you're right, it does say that. I somehow managed to miss it when
searching bash(1) for 'bashrc' before, but it's right there in the first
batch of results.

I apologize for the false trail.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

[toc] | [prev] | [next] | [standalone]

#165894

On 24/03/16 00:30, David Wright wrote:
> ...
>
> I don't know what you mean by   "login" script   because you haven't
> yet told us (I believe) what your machine is configured to do when
> you boot it up. If you've installed some sort of Desktop Environment,
> then the DE has the responsibility of selecting the shell that runs
> your   "login" script   and, indeed, what the filename of that script
> is.
>
>
You're right - I didn't explicitly tell you that my desktop environment 
is Mate which I chose when I installed Debian recently. There's a 
"Control Centre" which has a GUI application "Startup Applications" 
which is pre-populated by items such as "GPG Password Agent", "Mate 
Settings Daemon", "Pulse Audio", etc. You can add your own item by 
specifying name and command. This is where I added a bash script I wrote 
which I called "Login" which is located in ~/bin. All my other scripts 
in there are run in a Mate terminal or via a launcher icon on the 
desktop, and in both cases they use the path set up in ~/.bashrc.

Anyway, thanks for the information (including the existence of dash). 
Unfortunately I don't have time to delve deeper into this now as I have 
another project that has reared its head, so I'd ask you not to spend 
any more of your time responding, as I will not revisit this thread. And 
thanks to all other responders for their efforts.

[toc] | [prev] | [next] | [standalone]

#165838

On 3/22/2016 11:20 AM, Russell Gadd wrote:
>
> Thanks for the export point which I have now used. However it doesn't 
> solve the problem.
>
> I experimented by adding the following line into ~/.bash_profile, 
> ~/.profile and ~/.bashrc:
> echo "This is <scriptname>" &>>/tmp/out.txt
>
> Neither of the profile files triggered the output, nor did .bashrc 
> until I manually opened a Mate terminal from the desktop. So it 
> appears that the profile files do not get invoked at any time.
>
> I've even tried changing the PATH which is set at the top of 
> /etc/profile, but this doesn't work either, so it looks like profile 
> files are ignored altogether.
>

I did a search using terms that seemed like likely suspects if I 
expected the login shell stuff to get
sourced when a display manager is handling the login instead of the shell.

The first page of results I got where some combination of old, 
incomplete, and/or GDM specific.
Even in the GDM case, I'm not sure if the documentation is correct for 
current versions of GDM
since I have not used GDM for a long time.

Sourcing '~/.profile' when the shell is not your login was more of a 
Redhat thing that other
distributions may or may not do.

I did see some bug reports which would probably have some relevant 
information in the
responses.

Create '~/.xprofile' and put your export commands and extra non-desktop 
specific stuff you
  always want to run there.

https://wiki.archlinux.org/index.php/xprofile

Later, Seeker

[toc] | [prev] | [next] | [standalone]

#165846

On 22/03/16 20:20, Seeker wrote:
> ...<see above>
>
> Create '~/.xprofile' and put your export commands and extra non-desktop
> specific stuff you
>   always want to run there.
>
> https://wiki.archlinux.org/index.php/xprofile
>
> Later, Seeker

Thanks. I might try this later.

[toc] | [prev] | [next] | [standalone]

#165841

On 3/22/2016 11:20 AM, Russell Gadd wrote:
>
> Thanks for the export point which I have now used. However it doesn't
> solve the problem.
>
> I experimented by adding the following line into ~/.bash_profile,
> ~/.profile and ~/.bashrc:
> echo "This is <scriptname>" &>>/tmp/out.txt
>
> Neither of the profile files triggered the output, nor did .bashrc
> until I manually opened a Mate terminal from the desktop. So it
> appears that the profile files do not get invoked at any time.
>
> I've even tried changing the PATH which is set at the top of
> /etc/profile, but this doesn't work either, so it looks like profile
> files are ignored altogether.
>

I did a search using terms that seemed like likely suspects if I 
expected the login shell stuff to get
sourced when a display manager is handling the login instead of the shell.

The first page of results I got where some combination of old, 
incomplete, and/or GDM specific.
Even in the GDM case, I'm not sure if the documentation is correct for 
current versions of GDM
since I have not used GDM for a long time.

Sourcing '~/.profile' when the shell is not your login was more of a 
Redhat thing that other
distributions may or may not do.

I did see some bug reports which would probably have some relevant 
information in the
responses.

Create '~/.xprofile' and put your export commands and extra non-desktop 
specific stuff you
  always want to run there.

https://wiki.archlinux.org/index.php/xprofile

Later, Seeker

[toc] | [prev] | [next] | [standalone]

#165843

[Multipart message — attachments visible in raw view] — view raw

On 3/22/2016 1:11 PM, Michael Fothergill wrote:
>
>
> On 22 March 2016 at 19:59, Dan Ritter <dsr@randomstring.org 
> <mailto:dsr@randomstring.org>> wrote:
>
>     On Tue, Mar 22, 2016 at 05:13:43PM +0000, Michael Fothergill wrote:
>     > On 22 March 2016 at 16:24, Andrew McGlashan <
>     > andrew.mcglashan@affinityvision.com.au
>     <mailto:andrew.mcglashan@affinityvision.com.au>> wrote:
>     >
>     > > Hi,
>     > >
>     > > On 23/03/2016 12:18 AM, Michael Fothergill wrote:
>     > > > I own a Samsung BD-C5900 Blu ray/DVD player.
>     > >
>     There's a reasonable chance that if you attack it with a
>     screwdriver, you will discover that there is a modern SATA
>     bluray/DVD drive in there, and you can rip it out and put
>     it in your computer.
>
>     -dsr-
>
>
> ​Would that drive be one that only read bluray and DVD disks or could 
> it be modified to burn them as well?
>

If the player did not have functions built in for recording the drive is 
probably just a reader, no
write capability.

It my reach a point where it makes more economic sense for the 
manufacturers to only create
RW drives than it does for them to have 2 production lines, but don't 
know if we are there yet,
much less if we were there when your player was manufactured.

Also I expect it's more likely that the player would have a laptop style 
drive in it which would
require an adapter to handle the different size of SATA data/power 
connectors if you are looking
to use it in a desktop system.

If the system you are looking to use it in is a laptop, then newer 
laptops that still include an
optical drive have gone to thinner drives. Outside of that it's a 
question of how things line up.
The piece that secures the drive to the laptop could probably be swapped 
with the piece off
of the old drive if necessary or left off if the drive fits tight enough 
if really necessary. The face
plate is less likely the match up between the two drives, especially 
between a DVD drive and a
Blue Ray drive.

Later, Seeker

[toc] | [prev] | [next] | [standalone]

#165844

[Multipart message — attachments visible in raw view] — view raw

See if this gets through, my WiFi got flaky, which seems like it cause some 
issue with imap between Thunderbird and Comcast. Thunderbird claims the 
message was sent twice, but I never got a copy in my inbox. 

Here we go again, from the webmail this time. ;) 



On 3/22/2016 11:20 AM, Russell Gadd wrote: 



Thanks for the export point which I have now used. However it doesn't 
solve the problem. 

I experimented by adding the following line into ~/.bash_profile, 
~/.profile and ~/.bashrc: 
echo "This is <scriptname>" &>>/tmp/out.txt 

Neither of the profile files triggered the output, nor did .bashrc 
until I manually opened a Mate terminal from the desktop. So it 
appears that the profile files do not get invoked at any time. 

I've even tried changing the PATH which is set at the top of 
/etc/profile, but this doesn't work either, so it looks like profile 
files are ignored altogether. 



I did a search using terms that seemed like likely suspects if I expected the login shell stuff to get 
sourced when a display manager is handling the login instead of the shell. 

The first page of results I got where some combination of old, incomplete, and/or GDM specific. 
Even in the GDM case, I'm not sure if the documentation is correct for current versions of GDM 
since I have not used GDM for a long time. 

Sourcing '~/.profile' when the shell is not your login was more of a Redhat thing that other 
distributions may or may not do. 

I did see some bug reports which would probably have some relevant information in the 
responses. 

Create '~/.xprofile' and put your export commands and extra non-desktop specific stuff you 
always want to run there. 

https://wiki.archlinux.org/index.php/xprofile 

Later, Seeker 

[toc] | [prev] | [next] | [standalone]

#165849

On Tuesday 22 March 2016 21:42:11 seeker5528@comcast.net wrote:
> See if this gets through, my WiFi got flaky, which seems like it cause some
> issue with imap between Thunderbird and Comcast. Thunderbird claims the
> message was sent twice, but I never got a copy in my inbox.

I got two earlier copies of each of two emails sent by you.  You can check the 
archives, rather than sending three copies, if you want to be sure!!  Been 
there, done that, got the tee shirt. ;-)

Lisi

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web