regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "André Kunz" <donatusmusic@gmx.de>,
	"Linux Stable" <stable@vger.kernel.org>,
	"Linux Input Devices" <linux-input@vger.kernel.org>,
	"Linux Regressions" <regressions@lists.linux.dev>
Cc: "Filipe Laíns" <lains@riseup.net>,
	"Bastien Nocera" <hadess@hadess.net>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>
Subject: Re: Found a bug with my gaming gear
Date: Mon, 20 Nov 2023 06:15:05 +0700	[thread overview]
Message-ID: <ZVqW-Ux7NM2958MR@archie.me> (raw)
In-Reply-To: <bd1a6eb1-a8af-4181-b9e4-c7b8d3af1eea@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]

On Thu, Nov 16, 2023 at 11:41:34PM +0100, André Kunz wrote:
> Hey there guys,
> 
> This is my first kernel "bug" report ever, so please bear with me if I
> didn't catch the precise right way to report this.
> 
> The bug I've found:
> 
> I'm running stable kernel 6.6.1-1 and as soon as I install it, many of
> my mouse's hardware buttons stop working. I have a Logitech G502 X Plus
> (it's a wireless mouse). As soon as I install 6.6.1 the mouse's hardware
> buttons won't work, i.e. only the two side-buttons would work, not the
> buttons (and/or my created profiles/macros) would. I have a few macros
> assigned to some buttons, which work perfectly fine under 6.5.11 (and
> earlier), but as soon as I'm on 6.6 they'd stop working.
> 
> Just wanted to report this and I hope there can be a fix.
> 

Thanks for the regression report. I'm adding it to regzbot:

#regzbot ^introduced: v6.5..v6.6
#regzbot title: only two side buttons of Logitech G502 X Plus works on kernel 6.6.1

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      parent reply	other threads:[~2023-11-19 23:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16 22:41 Found a bug with my gaming gear André Kunz
2023-11-17 13:49 ` Greg KH
2023-11-17 15:01 ` Hans de Goede
2023-11-19 23:15 ` Bagas Sanjaya [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=ZVqW-Ux7NM2958MR@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=donatusmusic@gmx.de \
    --cc=hadess@hadess.net \
    --cc=lains@riseup.net \
    --cc=linux-input@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).