linux-kernel - Re: 2.6.31-rc6 (yeah, I know...): weird tty / X.org state currently

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20090910172244.71282526EC9@mailhub.coreip.homeip.net>
Date:	Thu, 10 Sep 2009 09:49:06 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Andreas Mohr <andi@...as.de>
Cc:	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: 2.6.31-rc6 (yeah, I know...): weird tty / X.org state currently

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/