On Thu, 9 Dec 2010 22:19:09 -0800
Daniel Hedlund <[email protected]> dijo:
>I'm guessing that when the Nvidia drivers were installed, their own
>versions of shared libraries (i.e. libGL.so.260.19.21) were installed
>into the /usr/lib64 directory and some symlinks were updated to point
>to their version (i.e. libGL.so.1 -> libGL.so.260.19.21). I'm also
>guessing that distro provided version of each shared library is still
>in that directory (i.e. libGL.so.1.2). When the Nvidia drivers were
>uninstalled, the symlinks weren't switched back. We can verify this
>by running the following:
>$ ls -l /usr/lib64/libGL*.so*
>$ for i in $(ls -d /usr/lib64/libGL*.so*); do echo $i...; rpm -qf $i;
>echo; done
# ls -l /usr/lib64/libGL*.so*
lrwxrwxrwx 1 root root 16 Nov 26 19:01 /usr/lib64/libGLEW.so.1.5 ->
libGLEW.so.1.5.5
-rwxr-xr-x 1 root root 377848 Aug 25 13:31 /usr/lib64/libGLEW.so.1.5.5
lrwxrwxrwx 1 root root 18 Dec 9 17:03 /usr/lib64/libGL.so.1 ->
libGL.so.260.19.21
-rwxr-xr-x 1 root root 445008 Nov 1 10:07 /usr/lib64/libGL.so.1.2
-rwxr-xr-x 1 root root 982568 Nov 1819:08 /usr/lib64/libGL.so.260.19.21
lrwxrwxrwx 1 root root 20 Nov 26 19:00 /usr/lib64/libGLU.so.1 ->
libGLU.so.1.3.070900
-rwxr-xr-x 1 root root 383128 Nov
110:07 /usr/lib64/libGLU.so.1.3.070900
>From the above apparently there is a library and a link to it, but
named libGL.20.260.19.21, not libnvidia-tls.so.260.19.21. I renamed the
link and tried to launch Fontmatrix. This time I got "error while
loading shared libraries: libGL.so.1: cannot open shared object file:
No such file or directory," where previously it was
libnvidia-tls.so.26.19.21 that it couldn't find.
For the second command, all of the libraries were owned by
mesa-libGL-7.9-2.fc14.x86_64, except:
/usr/lib64/libGL.so.260.19.21...
file /usr/lib64/libGL.so.260.19.21 is not owned by any package
So I reinstalled mesa-libGL and it recreated the link that I had
renamed. WTH? Of course, recreating the link means Fontmatrix is back
telling me that it can't find libnvidia-tls.so.260.19.21.
>Chances are that there's the .so.1 version of the library which is a
>symlink and two other files. Changing the symlink to point to the
>version that's being managed by a distro package should fix some of
>the issues. Rather that doing it manually, reinstalling the RPM might
>work. To get the name of the RPM that controls the symlink:
>$ rpm -qf /usr/lib64/libGL.so.1
>
>You can run the above for each of the files you listed and try to
>reinstall each one:
Here are the results of the rpm -qf commands:
/libcucul.so.0.99.17 >
libcaca-0.99-0.10.beta17.fc14.x86_64
/libkdeinit4_plasma-desktop.so >
kdebase-workspace-4.5.3-3.fc14.x86_64
/libkdeinit4_ksmserver.so >
kdebase-workspace-4.5.3-3.fc14.x86_64
/libGL.so.1 >
mesa-libGL-7.9-2.fc14.x86_64
/libplasmagenericshell.so.4.5.0 >
kdebase-workspace-libs-4.5.3-3.fc14.x86_64
/libkworkspace.so.4.5.0 >
kdebase-workspace-libs-4.5.3-3.fc14.x86_64
/libfltk_gl.so.1.1 >
fltk-1.1.10-2.fc14.x86_64
/libcucul.so.0 >
libcaca-0.99-0.10.beta17.fc14.x86_64
/cinepaint/0.22-1/plug-ins/icc_examin_cp >
cinepaint-libs-0.22.1-19.fc14.x86_64
/libglut.so.3.9.0 >
freeglut-2.6.0-5.fc14.x86_64
/usr/lib64/libkwineffects.so.1 >
kdebase-workspace-libs-4.5.3-3.fc14.x86_64
/libclutter-gtk-0.10.so.0.0.0 >
clutter-gtk-0.10.8-2.fc14.x86_64
/usr/lib64/libGLEW.so.1.5 >
glew-1.5.5-1.fc14.x86_64
/libftgl.so.2.1.3 >
ftgl-2.1.3-0.3.rc5.fc13.x86_64
/libplasma.so.3 >
kdelibs-4.5.3-3.fc14.x86_64
/libcaca.so.0.99.17 >
libcaca-0.99-0.10.beta17.fc14.x86_64
/libcaca.so.0 >
libcaca-0.99-0.10.beta17.fc14.x86_64
/libplasma.so.3.0.0 >
kdelibs-4.5.3-3.fc14.x86_64
/libkdeinit4_kwin.so
kdebase-workspace-4.5.3-3.fc14.x86_64
/libGLU.so.1 >
mesa-libGLU-7.9-2.fc14.x86_64
/libGL.so.260.19.21 >
file /usr/lib64/libGL.so.260.19.21 is not owned by any package
/libkwineffects.so.1.0.0 >
kdebase-workspace-libs-4.5.3-3.fc14.x86_64
/libkdeinit4_ksysguard.so >
kdebase-workspace-4.5.3-3.fc14.x86_64
/libplasmagenericshell.so.4 >
kdebase-workspace-libs-4.5.3-3.fc14.x86_64
/libclutter-gtk-0.10.so.0 >
clutter-gtk-0.10.8-2.fc14.x86_64
/libftgl.so.2 >
ftgl-2.1.3-0.3.rc5.fc13.x86_64
/libGLU.so.1.3.070900 >
mesa-libGLU-7.9-2.fc14.x86_64
/libkdeinit4_krunner.so >
kdebase-workspace-4.5.3-3.fc14.x86_64
/libglut.so.3 >
freeglut-2.6.0-5.fc14.x86_64
/libkworkspace.so.4 >
kdebase-workspace-libs-4.5.3-3.fc14.x86_64
/libkdeinit4_plasma-windowed.so >
kdebase-workspace-4.5.3-3.fc14.x86_64
/libGLEW.so.1.5.5 >
glew-1.5.5-1.fc14.x86_64
This is a total of ten packages, and I reinstalled all of them. No
change in Fontmatrix or Ksysguard, but Cinepaint now shows an initial
installation splash screen, and then gives "cinepaint fatal error:
sigsegv caught" and offers to Exit or do a Stack Trace. I just exited.
I think the link idea is on the right track. I just haven't got it
right yet.
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
