Installed libx11 update from Slackware - Window Mgr Problem

[solex]

theru,

I have the symbolic links as you have stated:

-rwxr-xr-x 1 root root 984 Oct 27 16:33 libX11.la
lrwxrwxrwx 1 root root 15 Nov 4 21:43 libX11.so -> libX11.so.6.3.0
lrwxrwxrwx 1 root root 15 Nov 4 21:43 libX11.so.6 -> libX11.so.6.3.0
-rwxr-xr-x 1 root root 1270576 Oct 27 16:34 libX11.so.6.3.0
-rwxr-xr-x 1 root root 949 Oct 27 16:33 libX11-xcb.la
lrwxrwxrwx 1 root root 19 Nov 4 21:43 libX11-xcb.so -> libX11-xcb.so.1.0.0
lrwxrwxrwx 1 root root 19 Nov 4 21:43 libX11-xcb.so.1 -> libX11-xcb.so.1.0.0
-rwxr-xr-x 1 root root 3016 Oct 27 16:34 libX11-xcb.so.1.0.0

The contents of xerrs.log:

/usr/bin/xinit: error while loading shared libraries: libX11.so.6: cannot open shared object file: Input/output error

Also every time I install a package I get the following error, not sure if this is related to the fact that I'm doing this all from the console

jwm-xdgmenu: error while loading shared libraries: libX11.so.6: cannot open shared object file: Input/output error

[Semme]

Those errors are on 6964?

[solex]

Those errors are on 6964?

The errors are from 6.3.2

[Semme]

So which build are you actually running?

[solex]

So which build are you actually running?

I'm running 6.9.6.4 and switched to 6.3.2 at the Grub menu to check theru suggestions.

[Semme]

Five days in.. I gather you're still trying to recover your 632 system?

[theru]

The only times I've encountered an input/output error was when there was some sort of filesystem corruption. This can lead to all sorts of unexpected behavior.

First let's see if the savefile is still sane. This can easily be done from 6.9.6.4 by using e2fsck -f <savefile.2fs>. The -f option forces a filecheck on filesystems that have previously been marked clean.

The e2fsck command also has a -b option that checks for bad blocks. I have no experience with that other then a quick test but I assume when using it on the savefile it checks that part of the harddrive for errors.

After the savefile has been checked, are the libx11 files still there? Are they of the correct size? If the size differs too much from the ones on the sfs file then they are probably corrupted.

If this doesn't solve the issue then you can try to replace the libx11 files in /usr/lib inside the savefile with either the ones from the sfs file or the install package. Maybe that will make a difference?

[solex]

Five days in.. I gather you're still trying to recover your 632 system?

No I'm not trying to recover, I had a proper back up and a clean 6.9.6.4 install.

At this point just doing some research (learning) along the lines of theru's suggestions.

[Semme]

OK, good. I'll let go..

One of Pups few shortcomings.. A full-blown Pac-Man!