[SOLVED] bash: command not found

Tunafish · 2011-12-22 18:16:37

Sector11 wrote:

@ johnraff
HUSTON WE HAVE A PROBLEM!!

big_smile

Glad i'm not the only one!

I'm using lightdm as login manager..

Sector11 · 2011-12-22 18:18:22

Tunafish wrote:

Sector11 wrote:
@ johnraff
HUSTON WE HAVE A PROBLEM!!

Glad i'm not the only one!
I'm using lightdm as login manager..

Yup, me too; lightdm.
It's always nice when you have company. big_smile

Last edited by Sector11 (2011-12-22 18:18:46)

xaos52 · 2011-12-22 18:24:10

This is the explanation: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636108
hehe

xaos52 · 2011-12-22 18:28:45

To see the value of the PATH variable when it executes your openbox autostart.sh, add this command to the autostart.sh

(echo $PATH > /tmp/path) &

openbox --reconfigure

and verify the content of /tmp/path

It works in a terminal because your .bashrc is sourced as part of the terminal startup.

VastOne · 2011-12-22 18:45:29

On the new Point Release, I had these issues as well..

Also noticed things like ifconfig no longer works because /sbin is no longer in the path

Query ... When you do a

export PATH=$PATH:/sbin

Does this permanently add /sbin or just for this session?

Tunafish · 2011-12-22 18:48:41

xaos52 wrote:

To see the value of the PATH variable when it executes your openbox autostart.sh, add this command to the autostart.sh
(echo $PATH > /tmp/path) &
openbox --reconfigure
and verify the content of /tmp/path
It works in a terminal because your .bashrc is sourced as part of the terminal startup.

cat /tmp/path:

/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

Thanks for the explanation... it's a bug... what should i do now?
Add export PATH=$PATH:$HOME/bin to ~/.config/openbox/autostart?
Or would it be better to source $HOME/.profile from .xsession (before openbox-session is started) ?

Last edited by Tunafish (2011-12-22 18:56:53)

VastOne · 2011-12-22 18:50:25

^ I add it to .bashrc

PATH=$PATH:$HOME/bin:/sbin

Tunafish · 2011-12-22 18:56:10

VastOne wrote:

^ I add it to .bashrc
PATH=$PATH:$HOME/bin:/sbin

Eh VastOne, that's what it's all about here.... that doesn't work hmm
At least not for everything... just when you open a terminal...

Last edited by Tunafish (2011-12-22 18:58:13)

VastOne · 2011-12-22 18:57:08

Tunafish wrote:

VastOne wrote:
^ I add it to .bashrc
PATH=$PATH:$HOME/bin:/sbin
Eh VastOne, that's what it's all about here.... that doesn't work

Just noticed that Tuna

Sorry for my gaffe...

EnochRoot · 2011-12-22 19:20:00

Adding it to your .bashrc will mean it is picked up when you run a terminal which will start a shell for you, likewise doing export PATH=$PATH:~/bin will add it only for that instance of the shell. Best solution is to put the full pathname into rc.xml, so call /home/username/bin/kfc.sh rather than kfc.sh

Other entries in rc.xml are working because the executables (scripts/binaries) are in your default path (usr/bin, usr/local/bin etc).

I used to have env vars etc in my .bash_profile and aliases / functions etc in my .bashrc but this meant having to ensure my xterms were started as a login session, in my view its easier to just run them as normal shells and have everything in the .bashrc but like so many things in Linux there are multiple ways of doing it

xaos52 · 2011-12-22 19:20:51

Let me install lightdm and see how it works.
Will come back with an answer.

xaos52 · 2011-12-22 19:32:11

Where did you guys get lightdm from?
You upgraded to testing or unstable?

VastOne · 2011-12-22 19:35:46

^ Correct... it is not in Stable .. you would need to grab the source

xaos52 · 2011-12-23 08:56:29

I think this is the easiest solution:

Create $HOME/.xsession

with this content

#!/bin/sh

if [ -e $HOME/.profile ]; then
    . $HOME/.profile
fi

exec openbox-session

This works for me. YMMV.

Tunafish · 2011-12-23 09:23:55

xaos52 wrote:

I think this is the easiest solution:
Create $HOME/.xsession
with this content
#!/bin/sh

if [ -e $HOME/.profile ]; then
    . $HOME/.profile
fi

exec openbox-session
This works for me. YMMV.

Thanks... works for me as well.
Tuna

chaanakya · 2011-12-23 11:39:56

Or you could

source ~/.bashrc

in autostart.sh

Sector11 · 2011-12-23 14:31:57

xaos52 wrote:

This is the explanation: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636108
hehe

Shame on you lightDM
grumble grumble GRRRRRRRRRRRRRRRRRRRRRRRRRR
OK they will fix it ... right!
OK they will fix it ... right!
OK they will fix it ... right!
OK they will fix it ... right! roll

xaos52 wrote:

This works for me. YMMV.

Tunafish wrote:

Thanks... works for me as well.
Tuna

works OK here too! +2 (first post)

Last edited by Sector11 (2011-12-23 14:42:24)

johnraff · 2011-12-23 17:01:30

chaanakya wrote:

Or you could
source ~/.bashrc
in autostart.sh

The stuff in .bashrc is intended for working in terminals. I don't think you'd want/need it in an x-session. (Anyway, .bashrc just returns if it doesn't find a terminal.)

xaos52's does sound like the easiest solution, though I wonder what the Approved Debian Way of setting personal environment variables would now be?

Last edited by johnraff (2011-12-23 17:42:00)

Awebb · 2011-12-23 17:19:49

I'd be patient with lightdm. They have plans and those plans will take time. If I understood the goals right, they try to provide a DM platform, instead of having 1000 different implementations with more or less minor differences. Ubuntu using lightdm might push it a little, I hope not in the wrong direction.

johnraff · 2011-12-23 17:40:42

...you could try creating ~/.xsessionrc , putting the PATH command in there and seeing if it gets executed? If it works, that might be the official substitute for .profile?

jelloir · 2012-03-05 10:38:02

Debian are not going to fix this for lightdm (refer to the Debian bug link xaos52 posted) so unless the upstream lightdm dev's change it then you will have to manually ensure ~/.profile or ~/.bash_profile are sourced.

I would suggest the best way to do this is per a response in that bug report. Simply source ~/.profile using ~/.xsessionrc then you still only need to make changes to ~/.profile.

So in ~/.xsessionrc simply insert

. /etc/profile
. ${HOME}/.profile

(or ${HOME}/.bash_profile if you are using that)

And be done with it.

Last edited by jelloir (2012-03-05 10:41:18)

CrunchBang Linux

SEARCH

#26 2011-12-22 18:16:37

Re: [SOLVED] bash: command not found

#27 2011-12-22 18:18:22

Re: [SOLVED] bash: command not found

#28 2011-12-22 18:24:10

Re: [SOLVED] bash: command not found

#29 2011-12-22 18:28:45

Re: [SOLVED] bash: command not found

#30 2011-12-22 18:45:29

Re: [SOLVED] bash: command not found

#31 2011-12-22 18:48:41

Re: [SOLVED] bash: command not found

#32 2011-12-22 18:50:25

Re: [SOLVED] bash: command not found

#33 2011-12-22 18:56:10

Re: [SOLVED] bash: command not found

#34 2011-12-22 18:57:08

Re: [SOLVED] bash: command not found

#35 2011-12-22 19:20:00

Re: [SOLVED] bash: command not found

#36 2011-12-22 19:20:51

Re: [SOLVED] bash: command not found

#37 2011-12-22 19:32:11

Re: [SOLVED] bash: command not found

#38 2011-12-22 19:35:46

Re: [SOLVED] bash: command not found

#39 2011-12-23 08:56:29

Re: [SOLVED] bash: command not found

#40 2011-12-23 09:23:55

Re: [SOLVED] bash: command not found

#41 2011-12-23 11:39:56

Re: [SOLVED] bash: command not found

#42 2011-12-23 14:31:57

Re: [SOLVED] bash: command not found

#43 2011-12-23 17:01:30

Re: [SOLVED] bash: command not found

#44 2011-12-23 17:19:49

Re: [SOLVED] bash: command not found

#45 2011-12-23 17:40:42

Re: [SOLVED] bash: command not found

#46 2012-03-05 10:38:02

Re: [SOLVED] bash: command not found

Board footer