linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Jiri Kosina <jkosina@suse.cz>,
	rjw@sisk.pl, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org, Mike Galbraith <efault@gmx.de>
Subject: Re: [regression] 2.6.30 leaking keys on console switch
Date: Thu, 15 Oct 2009 21:59:24 -0700	[thread overview]
Message-ID: <20091016045924.GD11582@core.coreip.homeip.net> (raw)
In-Reply-To: <20090716092406.GC8046@one.firstfloor.org>

On Thu, Jul 16, 2009 at 11:24:06AM +0200, Andi Kleen wrote:
> > Andi, are you absolutely sure that this appeared between .29 and .30 for 
> > you?
> 
> I only noticed it after the .30 update at least.
> 
> > And if so, is there any chance you could try bisecting it?
> 
> Ok.
> 
> > 
> > (*) have been on virtual desktop where firefox was running, switched to 
> > console using Ctrl-Alt-F1, and switched back to X using F7. Firefox then 
> > popped up some dialog about configuring some feature that is triggered by 
> > pressing F7/AltF7, or whatever. Is that what you are seeing?
> 
> Yes, I typically see it with the help screen. It also happens with
> other applications, not just firefox.
> 

I don't really see the issue here, except for maybe X being stupid - it
seems that it processes release events as press+release in cases when it
did not see the press event.

Start up xev, switch to text console and then back to X (don't release
the CTRL+ALT+Fx combo). Let X switch fully and then release the combo.
Observe the 2 events reported by xev for Fx key. You may try running
evtest in other window and observe that there are no down events at the
time of 2 xev events, only autorepeats and release event (and
autorepeats are ignored by X who does it's own software autorepeat).

-- 
Dmitry

      reply	other threads:[~2009-10-16  5:00 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07  8:44 [regression] 2.6.30 leaking keys on console switch Andi Kleen
2009-07-07  8:50 ` Jiri Kosina
2009-07-07  9:12   ` Andi Kleen
2009-07-07  9:15     ` Jiri Kosina
2009-07-08  6:53   ` Dmitry Torokhov
2009-07-08 11:20     ` Jiri Kosina
2009-07-09 11:29       ` Jiri Kosina
2009-07-09 20:01         ` Andi Kleen
2009-10-14  4:58       ` Dmitry Torokhov
2009-10-14  7:19         ` Andi Kleen
2009-10-14  7:39           ` Dmitry Torokhov
2009-10-14  7:50             ` Dmitry Torokhov
2009-10-16  5:41             ` H. Peter Anvin
2009-10-19 21:38             ` Pavel Machek
2009-10-21  8:15               ` Dmitry Torokhov
2009-10-23 20:29                 ` Pavel Machek
2009-07-09 11:20     ` Jiri Kosina
2009-07-09 12:00       ` Andi Kleen
2009-07-09 20:03       ` Andi Kleen
2009-07-09 21:58         ` Jiri Kosina
2009-07-13  4:05       ` Dmitry Torokhov
2009-07-13  7:07         ` Jiri Kosina
2009-07-13  8:25           ` Andi Kleen
2009-07-16  9:02             ` Jiri Kosina
2009-07-16  9:24               ` Andi Kleen
2009-10-16  4:59                 ` Dmitry Torokhov [this message]

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=20091016045924.GD11582@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=efault@gmx.de \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).