> >
> > I did a major upgrade (including "libc6"), had to rerun "apt-get upgrade"
> > several times. When I first noticed the problem, all users seemed to be
> > affected, then, when all packages were upgraded, some accounts behaved
> > correctly again, but not all! Weird indeed...
> >
> > And no, I didn't change the permissions.
> > [Now, I've just tried to add a line with "/lib" in "ld.so.conf", ran
> > "ldconfig", but it doesn't work any better.]
> >
>
> Looks like a bug for me in the update system, well, if all relative paths
> are already in ld.so.conf then must work in theory, look, normaly librt
> it's in /usr/li,b so add this path too and try again,
Tried that, no luck :-(
> ah when you run
>
> ldd $(which ls)
>
> what's the output with root and the other users?
>
# ldd $(which ls)
linux-gate.so.1 => (0xffffe000)
librt.so.1 => /lib/librt.so.1 (0xb7f59000)
libacl.so.1 => /lib/libacl.so.1 (0xb7f53000)
libselinux.so.1 => /lib/libselinux.so.1 (0xb7f3e000)
libc.so.6 => /lib/libc.so.6 (0xb7dfb000)
libpthread.so.0 => /lib/libpthread.so.0 (0xb7de4000)
/lib/ld-linux.so.2 (0xb7f77000)
libattr.so.1 => /lib/libattr.so.1 (0xb7de0000)
libdl.so.2 => /lib/libdl.so.2 (0xb7ddb000)
libsepol.so.1 => /lib/libsepol.so.1 (0xb7d9b000)
$ ldd $(which ls)
/bin/sh: error while loading shared libraries: libc.so.6: cannot open shared
object file: No such file or directory
/bin/bash: error while loading shared libraries: libdl.so.2: cannot open shared
object file: No such file or directory
:-{
Gilles
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
