It seems like everytime I install textlive distro on one of my computers I have the same problem:
peter@msideb:~$ tlmgr --gui
bash: tlmgr: command not found
The below reflects the current state of my .profile:
# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.
# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022
# if running bash
if [ -n "$BASH_VERSION" ]; then
# include .bashrc if it exists
if [ -f "$HOME/.bashrc" ]; then
. "$HOME/.bashrc"
fi
fi
# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi
PATH=/home/peter/texlive/2011/bin/i386-linux:/home/peter/bin/:$PATH; export PATH
MANPATH=/home/peter/texlive/2011/texmf/doc/man:$MANPATH; export MANPATH
INFOPATH=/home/peter/texlive/2011/texmf/doc/info:$INFOPATH; export INFOPATH
My system: Deb 6 testing, 32 bit, xfce desktop environment.
And yes, I did log off after I edited the .profile file.
Yes, I appear to have the .bashrc file:
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples
# If not running interactively, don't do anything
[ -z "$PS1" ] && return
# don't put duplicate lines in the history. See bash(1) for more options
# don't overwrite GNU Midnight Commander's setting of `ignorespace'.
HISTCONTROL=$HISTCONTROL${HISTCONTROL+:}ignoredups
# ... or force ignoredups and ignorespace
HISTCONTROL=ignoreboth
# append to the history file, don't overwrite it
shopt -s histappend
# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize
# make less more friendly for non-text input files, see lesspipe(1)
#[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"
# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi
# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color) color_prompt=yes;;
esac
# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes
if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi
if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt
# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
;;
*)
;;
esac
# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'
#alias grep='grep --color=auto'
#alias fgrep='fgrep --color=auto'
#alias egrep='egrep --color=auto'
fi
# some more ls aliases
#alias ll='ls -l'
#alias la='ls -A'
#alias l='ls -CF'
# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.
if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi
# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if [ -f /etc/bash_completion ] && ! shopt -oq posix; then
. /etc/bash_completion
fi
\usr/texbin? If you type the PATH command into your shell manually, doeswhich tlmgrfind it? – Peter Grill Sep 09 '11 at 02:11/home/peter/texlive/2011, so isn't that going to be my path? – ptrcao Sep 09 '11 at 02:45PATHcommand from your .profile into your command line and see if that sets the path correctly. If so, then you need to find out why the .profile is not being executed. If it doesn't result in the correct path, then you need to fix that path. – Peter Grill Sep 09 '11 at 03:05$ echo $PATHand post the result? By the way, on the third line from the bottom of your.profile, you do not need to specifically include/home/peter/binin your path, it should already be included by the conditional block immediately above that. – Jan Hlavacek Sep 09 '11 at 04:02$ echo $PATHgives:/usr/local/bin:/usr/bin:/bin:/usr/games. What does that tell you? – ptrcao Sep 09 '11 at 06:19PATH=/home/peter/texlive/2011/bin/i386-linux:$PATH; export PATHinto terminal and then runtlmgr --gui, it works! So you may be right, it isn't executing .profile for some reason. What do I need to do now? – ptrcao Sep 09 '11 at 06:26~/.bash_profileor~/.bash_login? – Andrew Stacey Sep 09 '11 at 06:38.bash_profile, then.bash_login, and finally.profileand it loads only one of these. Also, it only loads this on login. It may be the case that logging in via X does not count as an actual login (see http://linuxgazette.net/161/okopnik.html) so this might never be read even if the other files aren't there. Try putting the code in.bashrcinstead. – Andrew Stacey Sep 09 '11 at 09:11export BASHRCWASREAD="bashrc was read"(with suitable changes). Then log out, log in, and tryecho $BASHRCWASREAD(and for each). Also, take a look in.xsession_errorsto see if there's anything obvious in there (maybe a syntax error in one of the files). Try alsosource .bashrc(and the others) from the command line to see if there are any errors. – Andrew Stacey Sep 09 '11 at 09:49