Re: Bash bashed by libc6 upgrade
> David Baron wrote:
> > Sid is now in its post-release fun state. After upgrading libc6, locales,
> > system was entirely broken. I booted up knoppix and made a few symlinks
> > and could now boot. Also saw most apps worked just fine ... if I was not
> > in bash. Bash gives errors about accessing the new library symlinks.
> > Everything else seems to use them just fine.
> >
> > Changed my user shell to plain sh (csh also works) so now I could log in
> > to consoles and kde would come up. Everything (but bash) seems to play.
> > The other shells do not work so well in KDE's konsole but this is
> > keyboard problems more than anything else (also no autocomplete).
> >
> > Here is what bash gives starting up:
> > uname: error while loading shared libraries: libc.so.6: cannot open
> > shared object file: No such file or directory
> > uname: error while loading shared libraries: libc.so.6: cannot open
> > shared object file: No such file or directory
> > bash: [: !=: unary operator expected
> > bash: [: too many arguments
> > bash: [: too many arguments
> > bash: [: =: unary operator expected
> > bash: [: too many arguments
> > bash: [: too many arguments
> > bash: [: too many arguments
> > bash: [: too many arguments
> > bash: [: too many arguments
> > bash: [: too many arguments
> > bash: [: =: unary operator expected
> > bash: [: =: unary operator expected
> > bash: [: =: unary operator expected
> > bash: [: =: unary operator expected
> > bash: [: =: unary operator expected
> > bash: [: =: unary operator expected
> > bash: [: =: unary operator expected
> > bash: [: =: unary operator expected
> > bash: [: =: unary operator expected
> > bash: [: =: unary operator expected
> > bash: [: too many arguments
> > bash: [: =: unary operator expected
> > sed: error while loading shared libraries: libc.so.6: cannot open shared
> > object file: No such file or directory
> > /bin/sh: error while loading shared libraries: libdl.so.2: cannot open
> > shared object file: No such file or directory
> > /bin/true: error while loading shared libraries: libc.so.6: cannot open
> > shared object file: No such file or directory
> >
> > Trying to run anything in bash will cite one of the above or one or two
> > other such libraries (symlinked).
> >
> > Workaround? Who's bug would this be?
>
> Which version of libc6 is this?
> 2.5.2 or 2.5.3?
> I think the bug is with libc6...
Latest on Sid is 2.5.2.
More on the problem:
The "upgrade" script is bloooey. It complains about a duplicate installation
and tells the user to get rid of it. The most dangerous thing one could
possibly futz with. This should be handled by the script and at least more
clearly documented. First I took off the /lib entries which is catastrophic.
Booted the knoppix and copied them back from where I had saved them. So I
guess the installer wanted the /usr/lib ones off. Taking them off was less
catastrophic. Putting them back does not help bash, however.
Bash, I believe, is actually working fine. Something when it starts up has no
path to either of the sets of symlinks so fails. /etc/profile is not
processed. Bash is now crippled.
----
I have no problem using other shells meanwhile that still work but they will
not use my /etc/profiles. Without this, thingies like KDEDIR or QTDIR are not
defined and the PATH is no what I have been using either. So how would I get
this stuff into sh, csh, sash, etc. Sh does read /etc/environment (which had
an outdated JAVA_HOME so how I realized this) so maybe there. How would one
get these to use the keyboard the way bash has been? Certainly can and do on
the knoppix.
Reply to: