From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: <Valdis.Kletnieks@vt.edu>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test7 + X11 + screen savers vs. user
Date: Sun, 12 Oct 2003 13:22:44 +0900 [thread overview]
Message-ID: <28fe01c39078$a4c0a630$5cee4ca5@DIAMONDLX60> (raw)
In-Reply-To: 200310111443.h9BEhr6s022474@turing-police.cc.vt.edu
Valdis Kletnieks replied to me:
>> 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.
> 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.
> 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.
next prev parent reply other threads:[~2003-10-12 4:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-11 9:00 2.6.0-test7 + X11 + screen savers vs. user Norman Diamond
2003-10-11 14:43 ` Valdis.Kletnieks
2003-10-12 4:22 ` Norman Diamond [this message]
2003-10-13 5:39 ` tconnors+linuxkernel1066023352
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='28fe01c39078$a4c0a630$5cee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.