Re: Cannot login to computer after upgrade to Lenny

[MoS <mosdev@free.fr>]

Le Mon, Jun 01, 2009 at 10:48:14PM +0200, Sven Joachim écrivait : 
> On 2009-06-01 17:04 +0200, MoS wrote:
> 
> > # su
> > bash: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory
> >
> > # cp
> > cp: missing file operand
> > Try `cp --help' for more information.
> 
> So cp works, but su does not.  I suspect this is because su is suid
> root, but do not really have an idea what exactly the problem is.  The
> dynamic linker ignores the LD_LIBRARY_PATH environment variable for
> setuid/setgid programs, do you have it set in your environment?  And
> does a non-setuid copy of su show the error?
> 
> See ld.so(8) for some background information.
> 
> Sven
> 
> 

Hi,
here are a few more tests :

# cd ~/bin
# cp -p /bin/su .
# ls -la
total 36K
4.0K drwxr-xr-x  2 root root 4.0K Jun  2 21:16 ./
4.0K drwxr-xr-x 18 root root 4.0K Jun  2 21:16 ../
 28K -rwsr-xr-x  1 root root  27K Nov 22  2008 su
# chmod u-s su
# ls -la
total 36K
4.0K drwxr-xr-x  2 root root 4.0K Jun  2 21:16 ./
4.0K drwxr-xr-x 18 root root 4.0K Jun  2 21:16 ../
 28K -rwxr-xr-x  1 root root  27K Nov 22  2008 su
# ldd ./su
	linux-gate.so.1 =>  (0xb7f87000)
	libpam.so.0 => /lib/libpam.so.0 (0xb7f68000)
	libpam_misc.so.0 => /lib/libpam_misc.so.0 (0xb7f65000)
	libc.so.6 => /lib/libc.so.6 (0xb7e27000)
	libdl.so.2 => /lib/libdl.so.2 (0xb7e23000)
	/lib/ld-linux.so.2 (0xb7f88000)
# ./su
bash: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory

# cat /etc/ld.so.conf
include /etc/ld.so.conf.d/*.conf

# cat /etc/ld.so.conf.d/i486-linux-gnu.conf
# Multiarch support
/lib/i486-linux-gnu
/usr/lib/i486-linux-gnu

# cat /etc/ld.so.conf.d/libc.conf
# libc default configuration
/usr/local/lib

-------------

There must be a reason, there always is, but from where I'm standing, it feels like a nightmare...
I have a similar problem with the "login" command, I can give login, password, then comes the motd, and the error.
Maybe some executable called during the login process is responsible ? Is there any way to get some traces from this process ? Does someone know what executables might be called ?
Maybe it has something to do with PAM ? (I'm pretty sure it was left out of the box)

Thanks in advance for any help or clue, and thanks again Sven
MoS