From: Josh Litherland <josh@emperorlinux.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0 mouse events across suspend-to-disk
Date: Thu, 09 Oct 2003 09:29:57 -0400 [thread overview]
Message-ID: <1065706196.2085.17.camel@Borogove> (raw)
This is probably an XFree bug, but it's only triggered by
suspend-to-disk so I thought I'd at least mention it. I have my X11
configured to read core pointer events from /dev/input/mice and
/dev/psaux. Since the PS/2 mouse now feeds the input layer, it's
reasonable to suspect that I might be getting some redundancy of events
when I migrate this config to 2.6. However, XFree seemed to be able to
pick this out at startup time and would correctly see the two dev nodes
as the same mouse, registering each event only once. After resuming
from suspend-to-disk, however, all mouse events would occur twice.
Shutting down and restarting X corrected this, chvt'ing out and back in
did not correct it. The 'correct' fix seems to be making X only watch
/dev/input/mice for events.
FWIW, the laptop is a Toshiba Portege 3490CT, and I noted this behaviour
on test6 and test7 before realizing it was probably X's fault. =D
--
Josh Litherland (josh@emperorlinux.com)
reply other threads:[~2003-10-09 13:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1065706196.2085.17.camel@Borogove \
--to=josh@emperorlinux.com \
--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.