linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>, linux-input@vger.kernel.org
Subject: Re: 6.5-rc2: keys autorepeating when they should not
Date: Sun, 23 Jul 2023 22:42:50 -0700	[thread overview]
Message-ID: <ZL4PWiinZbeOcvFE@google.com> (raw)
In-Reply-To: <ZL0b/odKy/GlEzJV@duo.ucw.cz>

Hi Pavel,

On Sun, Jul 23, 2023 at 02:24:30PM +0200, Pavel Machek wrote:
> Hi!
> 
> I updated to 6.5-rc2, and now I see keyboard problems (in X). ~ once
> in two days I get keyboard "stuck", autorepeating. It is USB keyboard,
> hitting another key cancels the autorepeat.

Sounds like keys are not released because autorepeat handled by X and
not the kernel. I am not sure what would cause this, there were no
changes to the input core recently... Maybe HID?

From which kernel did you update to 6.5-rc2? Any chance you could try
bisecting?

Thanks.


-- 
Dmitry

      reply	other threads:[~2023-07-24  5:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-23 12:24 6.5-rc2: keys autorepeating when they should not Pavel Machek
2023-07-24  5:42 ` 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=ZL4PWiinZbeOcvFE@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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;
as well as URLs for NNTP newsgroup(s).