2.6.0-test7 + X11 + screen savers vs. user
In 2.6.0-test1 through test7, when running X11, the screen saver kicks in about every 5 minutes. I haven't checked the configuration but have confidence that it's obeying the timing correctly. The problem is that it doesn't care whether the keyboard and mouse have been used during that time. When the screen saver is running, any keyboard or mouse activity will restore the screen. Also when the screen saver isn't running, the focused window gets the input. But it's irritating to be in the middle of typing or mousing and suddenly lose a character or click because the screen saver kicked in and gobbled up the next event.
Quoted 4 lines · Norman Diamond
In 2.6.0-test1 through test7, when running X11, the screen saver kicks in about every 5 minutes. I haven't checked the configuration but have confidence that it's obeying the timing correctly. The problem is that it doesn't care whether the keyboard and mouse have been used during that time.
Which screen saver is this?
jwz's xscreensaver 4.13 mostly works for me with XFree86 4.3.0, and notices keyboard activity and mouse cursor movement, but fails to detect mouse button events - so if you're in a mail program and reading a lot of mail and hitting 'delete' over and over, the screensaver can kick in anyhow.
I have to admit I've not tracked down if this is xscreensaver's fault, or the X server's fault, or the kernel's fault.
Valdis Kletnieks replied to me:
Quoted 7 lines
Quoted 5 lines
In 2.6.0-test1 through test7, when running X11, the screen saver kicks in about every 5 minutes. I haven't checked the configuration but have confidence that it's obeying the timing correctly. The problem is that it doesn't care whether the keyboard and mouse have been used during that time.
Which screen saver is this?
In SuSE 8.2, KDE's configuration panel, it is "random". It was installed that way by default during installation (at least when X11 and KDE defaults are installed by default). The list of possible screen savers is too long to copy by hand, but anyway it doesn't seem to matter which one gets randomly selected. Under kernel 2.6.0-test1 through test7, the portion of KDE or X11 that is supposed to be informed of keyboard or mouse activity doesn't seem to be informed. The screen saver kicks in every 4 minutes according to KDE's configuration panel, which was also the default, and my estimate of 5 minutes was before looking at the settings.
Quoted 5 lines
jwz's xscreensaver 4.13 mostly works for me with XFree86 4.3.0, and notices keyboard activity and mouse cursor movement, but fails to detect mouse button events - so if you're in a mail program and reading a lot of mail and hitting 'delete' over and over, the screensaver can kick in anyhow.
Originally I thought I was observing something like this, but then watched more closely and it is broader. Mouse cursor movement is indeed being ignored. I'm almost certain that keyboard input is also being ignored, but maybe should conduct another test while watch watching.
Quoted 2 lines
I have to admit I've not tracked down if this is xscreensaver's fault, or the X server's fault, or the kernel's fault.
Under kernels 2.4.20, 2.4.19, and 2.4.18, I did not observe such a problem. The screen saver only kicked in after a period of inactivity. However, the communication failure among the kernel, X11, KDE, etc., might not necessarily be the kernel's fault, if other components were depending on some characteristic of the 2.4 series which was undocumented or deprecated in 2.4 and/or intentionally removed in 2.6.
"Norman Diamond" <[email protected]> said on Sat, 11 Oct 2003 18:00:45 +0900:
Quoted 9 lines
In 2.6.0-test1 through test7, when running X11, the screen saver kicks in about every 5 minutes. I haven't checked the configuration but have confidence that it's obeying the timing correctly. The problem is that it doesn't care whether the keyboard and mouse have been used during that time. When the screen saver is running, any keyboard or mouse activity will restore the screen. Also when the screen saver isn't running, the focused window gets the input. But it's irritating to be in the middle of typing or mousing and suddenly lose a character or click because the screen saver kicked in and gobbled up the next event.
What was this about time jumping backwards for some people?
Follow this thread:
http://www.ussg.iu.edu/hypermail/linux/kernel/0310.1/0056.html
Could trigger the screensaver if it thinks MAXINT time has elapsed :)
Signature · 4 lines
TimC -- http://astronomy.swin.edu.au/staff/tconnors/
When some other esteemed editor reposts this, it'll be the Periodic
Periodic Table Table story, and I will be even happier. ;^)
-- Emil Brink on /., about the periodic table table.