Description of problem: After upgrading from XFree86 to xorg xscreensaver doesn't work anymore Version-Release number of selected component (if applicable): xorg-x11-0.0.6.6-0.0.2004_03_11.6 How reproducible: 100% Steps to Reproduce: 1. Don't touch the computer for a while Actual results: The screen is never blanked Expected results: The screen should be blanked after configured amount of time Additional info: I had to change my mouse from using /dev/psaux to /dev/input/mice because it went crazy using /dev/psaux when upgrading to xorg. Using home rolled 2.6.3 kernel.
Correction: It isn't 100%, it just seems to happen sometimes. Running in verbose mode I get complaints about there being no keyboard or mouse data in /proc/interrupts. I also get the following error: XF86MiscSetGrabKeysState(1) returned MiscExtGrabStateAlready. Don't know what's relevant...
This is has started happening to me as of yesterday as well. I am using the latest xorg-x11 with the latest kernel from Raw Hide. This is on an i865G P4 system with a GeForce MX 440 AGP card (stock nv module). If left "blanking" for long periods of time, not only it doesn't activate DPMS, it doesn't unblank to normal operation, either. I can log into the box, though, and kill X. chvt will just hang, until I suspend or kill it, and vt7 will remain the current console. Let me know if there's anything else I can try to pin down the problem.
I've detected another thing that may be related. Since installing xorg sometimes (while I'm actively using my computer) my monitor switches off (showing a "no input" message, exactly like when dpms:ing off) and as soon as I touch mouse or keyboard it switches on again. This doesn't happen when xscreensaver is deactivated, so it seems that sometimes xscreensaver thinks I haven't touched my computer in half an hour even though it's sometimes less than half a minute since last input. It simply seems that there's some bug in the way xorg is feeding screensaver idle data...
I haven't had any problems with this in the last month or so. Guess things were fixed in xorg. Is it ok to close it?
I also have not seen any problems with this in rawhide, and no one else has mentioned any problems. Go ahead and close this, Daniel. -Chris Kuivenhoven