linux-kernel - Re: [PATCH 3/4] tty/vt/keyboard: reset the LEDs state at each console change

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] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 27 Jan 2017 19:18:11 +0100
From:   Benjamin Tissoires <benjamin.tissoires@...hat.com>
To:     Samuel Thibault <samuel.thibault@...-lyon.org>,
        Dmitry Torokhov <dmitry.torokhov@...il.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Jiri Slaby <jslaby@...e.com>, linux-input@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/4] tty/vt/keyboard: reset the LEDs state at each
 console change

On Jan 27 2017 or thereabouts, Samuel Thibault wrote:
> Hello,
> 
> Benjamin Tissoires, on Fri 27 Jan 2017 18:13:17 +0100, wrote:
> > When switching back from Gnome, the VT is not aware of the
> > current state of the LEDs. So if Gnome changes them, the
> > kernel still bellieves they are off, and it won't turn them
> > off when switching to a new TTY.
> 
> I'm not getting that issue, please detail which graphical stack you are
> using (Xorg/Wayland? input-libinput?)

Well, libinput won't have anything to do here, and the issue applies on
Gnome and gdm with both Xorg and Wayland. Given that you don't have the
issue, I had a feeling that it might be logind interfering (given that
it revokes the input file descriptor). So I tested a startx from root,
and indeed the issue is not present in that case.

I'll check with the systemd guys if this is something that comes from
them and if this can be fixable.

Cheers,
Benjamin

> 
> Samuel