Bug 12791
Summary: | xlock does not run! | ||
---|---|---|---|
Product: | [Retired] Red Hat Raw Hide | Reporter: | Sammy <sait.a.umar> |
Component: | xlockmore | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1.0 | CC: | rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-08-07 04:20:50 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sammy
2000-06-21 19:02:01 UTC
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? |