Error while loading shared libraries?!

[jeremy28]

Hi all;

I have ubuntu 9.04 on my Virtual Machine and my host OS is Win.XP,
I've installed SSH on my linux and and now, I use PuTTY on Win.XP to connect to the SSH on linux,

Now, I have a problem:
When I login with "root" and run any command, I see load errors for libraries such below:

vim:  error while loading shared libraries: libm.so.6: cannot open shared object file: No such file or directory
ls:  error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory
./shmop:  error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
…

I've defined a user in ubuntu and when I login with it, I have no problem in running commands!
Also, when I use "su" command in the user's session and go to the root, I have no problem again in running commands!

Could you help me where the problem is coming from?

Is it related to my linux version or distro?

Or anything else?!

TIA.

[devils casper]

root login in GUI has been disabled in Ubuntu? Have you enabled it? How do you login as "root"?
You should use sudo to gain root privileges instead of login as root user.

[Rubberman]

At a guess, you have incorrectly modified the .bash_profile or .bashrc files for root, probably the LD_LIBRARY_PATH environment variable, so it cannot find the libraries. Another possibility is that it has been chroot'd so /usr/lib or /usr/lib64 are not available.

Note that when you su to root without a trailing dash you keep your user environment, which is why I think you have done something to mung up the root user environment.

[jeremy28]

Hi and Thanks!

Here is my ".bashrc file" in root:

# ~/.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'.
export HISTCONTROL=$HISTCONTROL${HISTCONTROL+,}ignoredups
# ... or force ignoredups and ignorespace
export 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

# 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 color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
    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'

# 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 ]; then
    . /etc/bash_completion
fi

And ".bash_profile" in root:

# .bash_profile

# Get the aliases and functions
if [ -f ~/.bashrc ]; then
	. ~/.bashrc
fi

# User specific environment and startup programs

PATH=$PATH:$HOME/bin

export PATH
unset USERNAME

#TZ='GST-2:30'; export TZ

export PATH
unset USERNAME
export LD_ASSUME_KERNEL=2.4
export ORACLE_BASE=/home/oracle
export ORACLE_HOME=$ORACLE_BASE/product/8.1.6
export ORACLE_SID=pki
export NLS_LANG=american
export NLS_DATE_FORMAT='YYYY-MM-DD HH24:MI:SS'
export ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
export PATH=$PATH:$ORACLE_HOME/bin

#. ~/bin/udb-env.sh

What's the problem?
And how could I fix it?

TIA.

[Rubberman]

At a guess, you have incorrectly modified the .bash_profile or .bashrc files for root, probably the LD_LIBRARY_PATH environment variable, so it cannot find the libraries. Another possibility is that it has been chroot'd so /usr/lib or /usr/lib64 are not available.

Note that when you su to root without a trailing dash you keep your user environment, which is why I think you have done something to mung up the root user environment.

Well, I just came across some notes I made while dealing with a similar situation on my system to the effect that running KDE seems to reset/clear the LD_LIBRARY_PATH environment variable, so it needs to be done manually or possibly in the KDE user startup/configuration scripts. I haven't yet tried the latter. I don't know if other window/desktop managers have similar problems, but this is a possibility. In my case, I need to add /usr/local/lib to my LD_LIBRARY_PATH environment to run a beta copy of Chrome that I installed in /usr/local..