Linux Input/HID development
 help / color / mirror / Atom feed
From: Andreas Mohr <andi@lisas.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Andreas Mohr <andi@lisas.de>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.31-rc6 (yeah, I know...): weird tty / X.org state currently
Date: Thu, 10 Sep 2009 18:42:32 +0200	[thread overview]
Message-ID: <20090910164232.GA27404@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <20090910165837.50544526EC9@mailhub.coreip.homeip.net>

Hi,

On Thu, Sep 10, 2009 at 09:25:00AM -0700, Dmitry Torokhov wrote:
> On Thursday 10 September 2009 03:31:26 am Andreas Mohr wrote:
> > Possibly the kernel's control key state got stuck in a weird state,
> > perhaps due to some input layer race conditions or so.
> >
> > Or is it X.org's input handling which is responsible for Ctrl-Alt-F1
> > etc. combos? I wouldn't think so...
> 
> X is solely responsible for handling input when active. It switches
> console in RAW mode which bypasses kernel processing) and does it's
> own thing. This includes switching VTs upon Ctrl-ALt-Fx.

OK, but what's puzzling is that there's no indication whatsoever that
there's any broken Ctrl activity (neither in konsole nor in a tty),
yet the tty gets switched readily as soon as only Alt-Fx gets pressed in
X.org. 

IOW (unless that's wrong) you're saying that it's X.org which has
a broken Ctrl key state (but solely when doing the Alt-Fx switch,
_not_ when doing Ctrl-L or regular letter input), not the kernel.

If so, would this problem warrant notifying X.org upstream,
or is it likely to be fixed in newer X.org releases?

Andreas Mohr

  reply	other threads:[~2009-09-10 16:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-10 10:31 2.6.31-rc6 (yeah, I know...): weird tty / X.org state currently Andreas Mohr
2009-09-10 16:25 ` Dmitry Torokhov
2009-09-10 16:42   ` Andreas Mohr [this message]
2009-09-10 16:49     ` Dmitry Torokhov

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=20090910164232.GA27404@rhlx01.hs-esslingen.de \
    --to=andi@lisas.de \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox