Red Hat Bugzilla – Bug 12791
xlock does not run!
Last modified: 2014-03-16 22:14:21 EDT
version xlockmore-4.16.1-3 gives the following message when executed: #xlock BUG IN DYNAMIC LINKER ld.so: dl-version.c: 217: _dl_check_map_versions: Assertion `needed != ((void *)0)' failed!
I can't reproduce this here. What does 'rpm -q glibc' say?
rpm -q glibc sais glibc-2.1.90-17 I have the latest (june 15) rawhide rpm's installed for everything but XF86, KDE, and kernel (I have 2.2.14-12). # ls -l xlock -rwxr-xr-x 1 root root 1683672 Jun 11 14:14 xlock*
What X libraries do you have installed?
Also, what happens if you do: rm -f /etc/ld.so.cache ldconfig ?
I have the X11 libraries that came with XFree86-4.0-0.16 from rawhide. doing rm -f /etc/ld.so.cache ldconfig worked fine BUT xlock still gives the same error! I downloaded the previous xlock binary from tape and that runs fine EXCEPT I could not log back in! Probably because of /etc/pam.d/xlock file.
OK. I tried to build xlock from the rpm source on rawhide. The compilation failed because I seem to be missing some GL headers or something since I get hundreds of messages like: /usr/src/redhat/BUILD/xlockmore-4.16.1/modes/glx/rubik.c:723: undefined referenc e to `glEnd' /usr/src/redhat/BUILD/xlockmore-4.16.1/modes/glx/rubik.c:726: undefined referenc e to `glBegin' I have only the NVIDIA's gl libraries. The previous xlock and all GL stuff work fine. PS: Also the /etc/pam.d/xlock seems to be incorrect
I still can't reproduce this here. Why do you say that the pam.d/xlock file looks incorrect?