For the last few XFree86 releases, the beforelight screensaver has been nonfunctional if ran with the XFree86 core server.
[mharris@asdf mharris]$ beforelight X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 113 (X_KillClient) Value in failed request: 0x1600001 Serial number of failed request: 20 Current serial number in output stream: 22 It fails as far back as 4.0.3 at least. After a bit of debugging.... I just debugged this for a while and beforelight itself seems to work ok, but what is failing is the X server somehow it seems. If you do a clean X server startup, then do: xset s 5 xset s activate beforelight It will come on in 5 seconds time. However, if you kill the beforelight process, then start it up again, you will get the errors we've put above. This is also testable inside Xnest by doing: xinit -- $(which Xnest) :1 It seems to me like some resource is being allocated in the X server when beforelight starts up the first time, but isn't getting released when it is sent SIGINT (or some other signal). This problem is 100% reproduceable every time for all releases I've tested it on (4.0.3, 4.1.0, 4.2.0, 4.2.1, CVS), and occurs on x86, Alpha, ia64 platforms at least. A BSD user also acknowledged the problem on IRC too. I fiddled with it for a brief while, however similar screensaver exists in xscreensaver, so I decided it wasn't worth time fixing. Nonetheless, I thought someone else might be interested in knowing about the problem as it seems to be an X server bug. If anyone is interested in debugging/troubleshooting further, I can provide more info. Probably best to disable beforelight at build time otherwise. TTYL -- Mike A. Harris ftp://people.redhat.com/mharris OS Systems Engineer - XFree86 maintainer - Red Hat _______________________________________________ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
