Linux Input/HID development
 help / color / mirror / Atom feed
From: Alerymin <alerdev.ca4x6@simplelogin.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: stable@vger.kernel.org,regressions@lists.linux.dev,dmitry.torokhov@gmail.com,linux-input@vger.kernel.org
Subject: Re: Bug report - Sticky keys acting not sticky sometimes
Date: Fri, 29 Aug 2025 12:05:35 +0000	[thread overview]
Message-ID: <175646914218.7.12773379431621187280.877650584@simplelogin.com> (raw)
In-Reply-To: <dd24398b-0d10-45d4-b93d-4377c017f2e7@leemhuis.info>


[-- Attachment #1.1: Type: text/plain, Size: 1590 bytes --]






On Friday, August 29th, 2025 at 11:58, Thorsten Leemhuis <regressions@leemhuis.info> wrote:

> 

> 

> Lo!
> 

> On 29.08.25 13:36, Alerymin wrote:
> 

> > Note:
> > The issue looks like it's from tty directly but I don't see who is the maintainer, so I email the closest I can get
> > 

> > Description:
> > In command line, sticky keys reset only when typing ASCII and ISO-8859-1 characters.
> > Tested with the QWERTY Lafayette layout: https://codeberg.org/Alerymin/kbd-qwerty-lafayette
> > 

> > Observed Behaviour:
> > When the layout is loaded in ISO-8859-15, most characters typed don't reset the sticky key, unless it's basic ASCII characters or Unicode
> > When the layout is loaded in ISO-8859-1, the sticky key works fine.
> > 

> > Expected behaviour:
> > Sticky key working in ISO-8859-1 and ISO-8859-15
> > 

> > System used:
> > Arch Linux, kernel 6.16.3-arch1-1
> 

> 

> Thx for the report. You CCed the regressions list, so please allow me to
> ask: what's the last version where this worked? And FWIW in case nobody
> comes around with an idea what might cause this any time soon: could you
> bisect[1] what's causing the problem? Ciao, Thorsten
> 

> [1]
> https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html

Well, I read the reporting page a bit too quickly so I CCed the regressions list while I shouldn't have, sorry. I've never seen it work normally, it's not a regression.
On a github issues on kbd-project legionus had a few ideas about it: https://github.com/legionus/kbd/issues/140

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 343 bytes --]

  reply	other threads:[~2025-08-29 12:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-29 11:36 Bug report - Sticky keys acting not sticky sometimes Mathieu
2025-08-29 11:57 ` Thorsten Leemhuis
2025-08-29 12:05   ` Alerymin [this message]
2025-08-29 12:38     ` Thorsten Leemhuis
2025-08-29 12:50       ` Alerymin

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=175646914218.7.12773379431621187280.877650584@simplelogin.com \
    --to=alerdev.ca4x6@simplelogin.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=stable@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