Bug 24780
Summary: | xlock hangs | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | ken_laird |
Component: | xlockmore | Assignee: | Harald Hoyer <harald> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | ken_laird, mharris |
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: | 2001-03-27 22:23:39 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
ken_laird
2001-01-23 23:42:07 UTC
DRI is hanging, almost certainly. Does any GL program function properly? Maybe you should turn off Load "GLcore" in /etc/X11/XF86Config-4 if it doesn't. You may test GL functionality with /usr/X11R6/lib/xscreensaver/atlantis contained in the xscreensaver package. OK. We ran atlantis for over an hour on the box where xlock hangs. It seemed to run fine. Try running xscreensaver manually from the commandline or xscreensaver-demo and go through each one one at a time to try and track down the offending screensaver. The problem is with xlock, not xscreensaver. xlock does not appear to invoke xscreensaver. As I mentioned earlier, I have already run xlock manually going through each of the themes listed in the man page. I did not find one that appeared to be the same as what is on the screen when it locks. Is there someone at Redhat who is familiar enough with xlock to suggest where it could be modified easily to log as it switches themes? I could do it myself, but I would rather not take the time to reverse engineer it if someone is already familiar with the code. Try commenting out "GLcore" and "dri" in your config. Does this help? Commenting out GLcore and dri results in xlock running for a few minutes and then dying . It doesn't appear to leave a core file. Hmm. I'm not familiar with xlock right now myself, however it is likely best to have the proper package maintainer look into it even though it is very likely an XFree86 bug. I'm going to reassign to see if we can track it down. To the original submitter - can you try out the latest XFree86 packages from rawhide, as well as the latest xlockmore and xscreensaver packages and see if the problem goes away. Not much sense in us taking too much time on this one if by chance the problem you're experiencing is fixed now. I am, even as we speak, working on packaging XFree86 4.0.3 for installation on all of our Linux boxes. I will run xlock and see if it hangs up still. I think you mean this mode: xlock -mode morph3d -inwindow -nolock I have now run xlock without arguments, which, I'm pretty sure is how WindowMaker runs it when you select the lock menu function. I have also run it in windowed mode as you specified. With XFree86 4.0.3, it no longer hangs. It was pretty reproduceable before, so I think it is safe to say that the problem is fixed. Beauty, I'm closing it as fixed in rawhide. |