LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)
-   -   fail to start xterm: "could not exec /usr/OSE/bash: No such file or directory" (https://www.linuxquestions.org/questions/linux-general-1/fail-to-start-xterm-could-not-exec-usr-ose-bash-no-such-file-or-directory-686254/)

freeindy 11-26-2008 03:02 AM

fail to start xterm: "could not exec /usr/OSE/bash: No such file or directory"
 
Hi,

I am running Ubuntu 8.10 and logged in a user via NIS.

I am having problems starting xterm from Run program window (ALT-F2). When the terminal opens, I get the failing message:
Could not exec /usr/OSE/bash: No such file or directory".

I have located the failure in my export setting:

declare -x SHELL="/usr/OSE/bash"

Where is this set? I can change it from my gnome-terminal but then have to run xterm from gnome-terminal which I have no intention to do.

Any ideas?

Thanks,
Indy

eggixyz 11-26-2008 10:27 PM

Hey there,

if you don't need all the opensource virtual box OSE stuff, you can get rid of it by doing:

apt-get remove virtualbox --purge

then check with dkpg --list|grep -i virtualb

to make sure no other ose packages exist.

Otherwise, you can find the config file like this (sorry, I don't have Ubuntu running in my Vmware right now):

dpkg --list|grep -i virtualb

and run

dpkg --list-files for each package.

Alternately, just string it all together:

dpkg --list|grep -i virtualb|while read x;do dpkg --list-files $x;done

or however you prefer to do it.

Hope that helps. Sorry I couldn't be more specific.

Happy Thanksgiving :)

, Mike

freeindy 11-27-2008 02:04 AM

Thanks for the info but I don't have Virutalbox installed or any vmware etc.

I think it's set due the NIS log in and some login script in my home folder. I have tried to grep the whole system but can't seem to find it...

Indy

eggixyz 11-28-2008 12:22 AM

Hey There,

If you're logging on with NIS is possible that the setting isn't even on your machine.

If you they give you the latitude to modify your own home directory init files, create a .bashrc (or add to whatever's already there) and export the SHELL variable in there. You may want to just exec the right bash in there instead (assuming it's in /usr/bin) - that would get around problems you might have if they set the SHELL variable to read only. That variable is useful in some instances, but actually can be set to anything without changing the shell you're in.

exec /usr/bin/bash

Best wishes :)

, Mike


All times are GMT -5. The time now is 11:10 AM.