mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Andreas Mohr <andi@lisas.de>
Cc: 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 09:49:06 -0700	[thread overview]
Message-ID: <20090910172244.71282526EC9@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <20090910164232.GA27404@rhlx01.hs-esslingen.de>

On Thursday 10 September 2009 09:42:32 am Andreas Mohr wrote:
> 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?

I don't follow X development unfortunately but I think it is a good
idea to ask there.

-- 
Dmitry

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-10 10:31 Andreas Mohr
2009-09-10 16:25 ` Dmitry Torokhov
2009-09-10 16:42   ` Andreas Mohr
2009-09-10 16:49     ` 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=20090910172244.71282526EC9@mailhub.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=andi@lisas.de \
    --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

all inboxes | Powered by JetHome®